Triple
T6393238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iapetus |
E143877
|
entity |
| Predicate | hasGlobalAsymmetry |
P70360
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [Iapetus, hasGlobalAsymmetry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalAsymmetry Context triple: [Iapetus, hasGlobalAsymmetry, yes]
-
A.
hasObservedAsymmetry
Indicates that one entity has detected or recorded an imbalance, difference, or non-uniformity in another entity or in a relationship between entities.
-
B.
asymmetric
Indicates that the relationship between two entities never holds in both directions simultaneously, so if it holds from A to B it cannot also hold from B to A.
-
C.
localSymmetry
Indicates that an entity exhibits symmetry within a localized region or subset of its structure, rather than across its entire extent.
-
D.
afterSymmetryBreakingGives
Indicates that one entity or state results from another specifically after a symmetry-breaking process has occurred.
-
E.
usesSymmetryGroup
Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0687f5c6c81909c835329c996b311 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.