Triple
T5855162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Granddaddy of Them All |
E130132
|
entity |
| Predicate | regularlyHeldSince |
P9196
|
FINISHED |
| Object | 1916 |
—
|
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: 1916 | Statement: [The Granddaddy of Them All, regularlyHeldSince, 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularlyHeldSince Context triple: [The Granddaddy of Them All, regularlyHeldSince, 1916]
-
A.
historicallyRecordedSince
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
-
B.
establishedAt
chosen
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
C.
officeHeldInPeriod
Indicates that an entity held a particular office or position during a specified time period.
-
D.
councilHeldBetween
Indicates that a council, meeting, or formal deliberative session was held involving the two specified entities as participating parties.
-
E.
yearHeld
Indicates the specific year during which an event, position, or status was held or took place.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.