Triple
T29435503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice League (DCEU team) |
E746560
|
entity |
| Predicate | existsBeforeEvent |
P56217
|
FINISHED |
| Object | Barry Allen’s timeline-altering actions in The Flash |
—
|
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: Barry Allen’s timeline-altering actions in The Flash | Statement: [Justice League (DCEU team), existsBeforeEvent, Barry Allen’s timeline-altering actions in The Flash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsBeforeEvent Context triple: [Justice League (DCEU team), existsBeforeEvent, Barry Allen’s timeline-altering actions in The Flash]
-
A.
existedBeforeEvent
chosen
Indicates that the subject entity was already in existence prior to the occurrence of the specified event.
-
B.
existedAtEvent
Indicates that an entity was present or in existence at the time a specific event occurred.
-
C.
hasPrecedingEvents
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
-
D.
heirBeforeEvent
Indicates that one entity is designated as the heir of another prior to a specified event occurring.
-
E.
eventBefore
Indicates that one event occurs earlier in time than another event.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66accf77c81908f0f4c1a67e05e47 |
completed | May 2, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:16 p.m.