Triple
T27775663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azadegan League clubs |
E699177
|
entity |
| Predicate | beneathLeague |
P10194
|
FINISHED |
| Object | Persian Gulf 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: Persian Gulf Pro League | Statement: [Azadegan League clubs, beneathLeague, Persian Gulf Pro League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beneathLeague Context triple: [Azadegan League clubs, beneathLeague, Persian Gulf Pro League]
-
A.
belowLeague
chosen
Indicates that one entity is in a lower league, division, or competitive tier than another entity.
-
B.
laterLeague
Indicates that one league occurs chronologically after another league in time or sequence.
-
C.
aboveLeague
Indicates that one entity is in a higher league, tier, or competitive level than another.
-
D.
developmentLeagueFor
Indicates that one entity serves as a developmental or minor league affiliate for another, typically higher-level, sports team or organization.
-
E.
sisterLeague
Indicates that two sports leagues are considered counterparts or partners at a similar level, often collaborating or aligned in status or structure.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6379ab2248190ac5eadadb9bd5e3b |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:05 p.m.