Triple
T22124510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference Coastal Division |
E546757
|
entity |
| Predicate | existenceDuringEvent |
P3824
|
FINISHED |
| Object | pre-AFL–NFL merger era |
—
|
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: pre-AFL–NFL merger era | Statement: [Western Conference Coastal Division, existenceDuringEvent, pre-AFL–NFL merger era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existenceDuringEvent Context triple: [Western Conference Coastal Division, existenceDuringEvent, pre-AFL–NFL merger era]
-
A.
confirmedPresenceOf
Indicates that the presence or existence of an entity has been verified as true or established with certainty.
-
B.
occurredDuring
chosen
Indicates that one event or action took place within the temporal span of another event or time period.
-
C.
existenceScope
Indicates the contextual or situational bounds within which an entity or condition is considered to exist or hold true.
-
D.
ownedDuring
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
-
E.
legalStatusDuringEvent
Indicates the legal status or condition an entity holds specifically during the time period of a given 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1298016e081909d00015ca516d9fd |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.