Triple
T183261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL–AFL merger |
E3923
|
entity |
| Predicate | successorLeague |
P78
|
FINISHED |
| Object | modern National Football League |
—
|
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: modern National Football League | Statement: [NFL–AFL merger, successorLeague, modern National Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLeague Context triple: [NFL–AFL merger, successorLeague, modern National Football League]
-
A.
runnerUpLeague
Indicates that an entity finished in second place in a league competition.
-
B.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
-
C.
successorProtocol
Indicates that one protocol directly follows and replaces another in sequence or versioning.
-
D.
originalLeague
Indicates the league or competition in which an entity (such as a team or club) initially participated or was first a member.
-
E.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592516748190a85ae58eec191f14 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566dfc388190988b1b42d5daaafe |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.