Triple
T5202106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sagittarius Stream |
E117415
|
entity |
| Predicate | ageOfDisruption |
P62448
|
FINISHED |
| Object | several billion years |
—
|
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: several billion years | Statement: [Sagittarius Stream, ageOfDisruption, several billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageOfDisruption Context triple: [Sagittarius Stream, ageOfDisruption, several billion years]
-
A.
disruptsContinuityOf
Indicates that one entity interrupts, breaks, or otherwise prevents the ongoing, uninterrupted progression or sequence of another entity or process.
-
B.
eraOfObsolescence
Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
-
C.
timeOfMajorReforms
Indicates the specific time period during which significant reforms or major changes took place.
-
D.
timePeriodOfMajorDestruction
Indicates the time span during which a major destructive event affecting the subject occurred.
-
E.
transitionYear
Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7ad9bdd88190ae8aa6f4aba695a7 |
completed | March 20, 2026, 4:50 p.m. |
Created at: March 20, 2026, 1:47 p.m.