Triple
T5007446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Styx |
E112530
|
entity |
| Predicate | equilibriumState |
P23956
|
FINISHED |
| Object | non-hydrostatic |
—
|
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: non-hydrostatic | Statement: [Styx, equilibriumState, non-hydrostatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equilibriumState Context triple: [Styx, equilibriumState, non-hydrostatic]
-
A.
ultimateState
Indicates the final or end condition that an entity or process ultimately reaches after all preceding stages or transitions.
-
B.
inState
chosen
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
C.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
D.
principalState
Indicates that an entity serves as the primary or main state associated with another entity or context.
-
E.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
- F. None of above.
Provenance (3 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.