Triple
T4134570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIFL Premiership |
E85121
|
entity |
| Predicate | foundedAsTopDivision |
P54052
|
FINISHED |
| Object | 1890 |
—
|
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: 1890 | Statement: [NIFL Premiership, foundedAsTopDivision, 1890]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsTopDivision Context triple: [NIFL Premiership, foundedAsTopDivision, 1890]
-
A.
foundedAsNHLDivision
Indicates that an NHL division was originally established or created in its initial form as part of the National Hockey League.
-
B.
foundedAsMajorLeagueClub
Indicates that an organization or team was originally established as a major league club at the time of its founding.
-
C.
typicalNumberOfTopDivisionTeams
Indicates the usual or standard number of teams that compete in the highest-level division of a league or competition.
-
D.
topDivision
Indicates that an entity belongs to the highest-level division or tier within a hierarchical structure.
-
E.
topDivisionOf
Indicates that one administrative or organizational unit is the highest-level division within the structure of another entity.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af039fb19c8190b20e62a3b3ad25c1 |
completed | March 9, 2026, 5:30 p.m. |
Created at: March 9, 2026, 3:43 p.m.