Triple
T29141342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andorra (MoraBanc Andorra) |
E738641
|
entity |
| Predicate | locatedInLeagueSystemOf |
P201522
|
FINISHED |
| Object | Spain |
—
|
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: Spain | Statement: [Andorra (MoraBanc Andorra), locatedInLeagueSystemOf, Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLeagueSystemOf Context triple: [Andorra (MoraBanc Andorra), locatedInLeagueSystemOf, Spain]
-
A.
locatedInLeagueStructure
Indicates that an entity occupies a specific position or level within an organized league’s hierarchical structure.
-
B.
basedInLeague
Indicates that an entity (such as a team or club) participates in, belongs to, or is officially associated with a particular league.
-
C.
isPartOfLeague
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
D.
hasSeparateLeagueSystemFor
Indicates that one entity organizes or maintains a distinct, independent league structure specifically for another entity or group.
-
E.
locationLeague
Indicates that an entity (such as a sports team or club) is associated with or participates in a particular league.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_6a000013004c8190a01710441f881fdc |
completed | May 10, 2026, 3:48 a.m. |
Created at: April 28, 2026, 11:36 a.m.