Triple
T27976148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranian league system |
E706495
|
entity |
| Predicate | topTierNameHistory |
P54355
|
FINISHED |
| Object | Iran Pro League |
—
|
NE NERFINISHED |
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: Iran Pro League | Statement: [Iranian league system, topTierNameHistory, Iran Pro League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topTierNameHistory Context triple: [Iranian league system, topTierNameHistory, Iran Pro League]
-
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.
historicalThirdTierName
Indicates that an entity previously held a third-tier name or designation in a historical naming or ranking system.
-
C.
historicalTopDivisionName
chosen
Indicates that an entity had a particular name for its top competitive division during a past period in its history.
-
D.
rankHistory
Indicates the historical sequence of ranks or positions an entity has held over time.
-
E.
topTierFoundedAsRoundRobin
Indicates that a top-tier competition was originally established using a round-robin format.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b398598819098799e9f2b5bc0bb |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:41 p.m.