Triple
T28785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC East |
E573
|
entity |
| Predicate | establishedInLeagueMerger |
P176
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [NFC East, establishedInLeagueMerger, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedInLeagueMerger Context triple: [NFC East, establishedInLeagueMerger, 1970]
-
A.
originLeague
Indicates the sports league or competition from which an entity (such as a team, player, or event) originally comes or is associated.
-
B.
originalLeague
Indicates the league or competition in which an entity (such as a team or club) initially participated or was first a member.
-
C.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
-
D.
mergerYear
chosen
Indicates the year in which two or more entities formally merged into a single entity.
-
E.
league
Indicates that an organization or team participates in, is a member of, or is associated with a particular sports or competitive 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24925607c8190a9ce7ec834f3e5bb |
completed | Feb. 28, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69a2486bd74c81908d32be3c7d22f51f |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.