Triple
T9910516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian football league system |
E185128
|
entity |
| Predicate | topTierFoundedAsRoundRobin |
P91108
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Italian football league system, topTierFoundedAsRoundRobin, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topTierFoundedAsRoundRobin Context triple: [Italian football league system, topTierFoundedAsRoundRobin, 1929]
-
A.
topTierUntil
Indicates that an entity holds a top-tier or highest-status position only up to a specified point in time, after which this status no longer applies.
-
B.
topTierRelation
Indicates a relationship in which one entity belongs to the highest or most elite level within a ranked or hierarchical set of entities.
-
C.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
D.
tier1Range
Indicates that something falls within the defined bounds or limits of the first (or primary) tier in a tiered range system.
-
E.
firstTier
Indicates that one entity occupies the highest or primary level, rank, or priority relative to others in a hierarchical structure.
- 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb512a26881908eb72a21ffb1efef |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:41 p.m.