Triple
T10430054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian football pyramid |
E245887
|
entity |
| Predicate | secondTierLevel |
P14825
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Norwegian football pyramid, secondTierLevel, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondTierLevel Context triple: [Norwegian football pyramid, secondTierLevel, 2]
-
A.
secondTier
Indicates that something occupies a secondary or subordinate level of importance, quality, or rank relative to a primary or top tier.
-
B.
secondLevelStructure
chosen
Indicates a relationship where one structure functions as a secondary or subordinate level within a larger, primary structure.
-
C.
secondLevelRepresents
Indicates that one entity serves as a secondary or subordinate representation of another, typically refining or detailing the primary representation.
-
D.
secondStage
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
-
E.
secondStageType
Indicates the specific kind or category of a process, object, or event that occurs as the second stage in a multi-stage sequence.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea62d6448190a7f5b785467824cf |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:13 p.m.