Triple
T29074973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundation franchise |
E735911
|
entity |
| Predicate | chronologyEndWork |
P179925
|
FINISHED |
| Object | Foundation and Earth |
—
|
NE NERFINISHED |
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: Foundation and Earth | Statement: [Foundation franchise, chronologyEndWork, Foundation and Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyEndWork Context triple: [Foundation franchise, chronologyEndWork, Foundation and Earth]
-
A.
chronologyEnd
Indicates that one event, state, or time interval marks the ending point or conclusion of another in a temporal sequence.
-
B.
chroniclesEndDate
Indicates the date on which a chronicle, record, or documented series of events concludes.
-
C.
chronologyStartWork
Indicates the point in time at which a work or project begins within a chronological sequence or timeline.
-
D.
chronologicalCoverageEnd
Indicates the point in time at which the temporal or chronological span of something (such as a resource, event, or record) comes to an end.
-
E.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 28, 2026, 10:22 a.m.