Triple
T202959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Four |
E4545
|
entity |
| Predicate | firstHeldAsNamedEvent |
P10207
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Final Four, firstHeldAsNamedEvent, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHeldAsNamedEvent Context triple: [Final Four, firstHeldAsNamedEvent, 1950s]
-
A.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
B.
TTFirstHeld
Indicates that an entity held a particular title, position, or item for the first time in a given context or sequence.
-
C.
firstEditionHeldIn
Indicates the location where the first edition or initial occurrence of an event was held.
-
D.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
E.
firstHeldInOmaha
Indicates that the first occurrence or edition of an event or activity took place in Omaha.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25f4602c081909e89de233cbc5670 |
completed | Feb. 28, 2026, 3:21 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.