Triple
T16481560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rory Williams |
E400329
|
entity |
| Predicate | timelineAffectedBy |
P25489
|
FINISHED |
| Object | crack in the universe |
—
|
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: crack in the universe | Statement: [Rory Williams, timelineAffectedBy, crack in the universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timelineAffectedBy Context triple: [Rory Williams, timelineAffectedBy, crack in the universe]
-
A.
timelineUse
Indicates that one entity utilizes or incorporates another entity within a temporal sequence or schedule (a timeline).
-
B.
chronologicalEffect
Indicates that one event or state occurs as a temporal consequence of, or in sequence after, another.
-
C.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
D.
affectedProject
Indicates that one entity has an impact on, or is influenced by, a particular project.
-
E.
effectOnSchedule
Indicates how an event, action, or condition changes, disrupts, or influences a planned schedule or timeline.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e02b2c881909576a23bfbd3123c |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.