Triple
T8048695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazfi Cup |
E187618
|
entity |
| Predicate | tierInIranianSystem |
P74340
|
FINISHED |
| Object | primary national cup |
—
|
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: primary national cup | Statement: [Hazfi Cup, tierInIranianSystem, primary national cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierInIranianSystem Context triple: [Hazfi Cup, tierInIranianSystem, primary national cup]
-
A.
tierInDomesticSystem
chosen
Indicates the hierarchical level or rank that an entity occupies within a country's internal (domestic) system or structure.
-
B.
tierInLeagueSystem
Indicates the specific hierarchical level or division an entity occupies within an organized league system.
-
C.
tierInFarmSystem
Indicates the specific hierarchical level or rank an entity occupies within a farm system structure.
-
D.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
E.
tier3Range
Indicates that one entity falls within the defined third-level (tier 3) range or interval relative to another entity or reference scale.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7711f48190af2002533c2e426a |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.