Triple
T30197881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Division (Southern Football League) |
E767684
|
entity |
| Predicate | foundedAsDivision |
P2612
|
FINISHED |
| Object | 1894 |
—
|
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: 1894 | Statement: [Premier Division (Southern Football League), foundedAsDivision, 1894]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsDivision Context triple: [Premier Division (Southern Football League), foundedAsDivision, 1894]
-
A.
introducedAsDivision
Indicates that one entity is presented or designated as a division or subdivision of another entity.
-
B.
hasFormerDivision
Indicates that an entity previously had another entity as one of its internal divisions or sub-units, but no longer does.
-
C.
foundedAsPartOf
chosen
Indicates that an entity was established as a component, division, or subset of a larger existing organization, project, or structure.
-
D.
foundedAsTopDivision
Indicates that an organization, competition, or league was originally established as the highest (top) division within its hierarchical structure.
-
E.
foundedAsOneOf
Indicates that an entity was originally established as one member of a group or set of entities founded together.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 29, 2026, 7:30 p.m.