Triple
T1000523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canis Major Dwarf Galaxy |
E21591
|
entity |
| Predicate | dynamicalState |
P3520
|
FINISHED |
| Object | being tidally disrupted |
—
|
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: being tidally disrupted | Statement: [Canis Major Dwarf Galaxy, dynamicalState, being tidally disrupted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynamicalState Context triple: [Canis Major Dwarf Galaxy, dynamicalState, being tidally disrupted]
-
A.
typeOfState
Indicates that one state is a specific kind or category of another, more general state.
-
B.
stateDance
Indicates a relationship where a state is associated with or designates an official dance.
-
C.
associatedState
chosen
Indicates that one entity is linked or connected to a particular state, condition, or status of another entity.
-
D.
stateRepresentation
Indicates that one entity serves as a depiction, model, or encoding of the condition, configuration, or status of another entity.
-
E.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fb18b88190ae2d620aaaff4f90 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.