Triple
T28963173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Andorra |
E731966
|
entity |
| Predicate | affiliatedConfederation |
P25674
|
FINISHED |
| Object | UEFA |
—
|
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: UEFA | Statement: [FC Andorra, affiliatedConfederation, UEFA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliatedConfederation Context triple: [FC Andorra, affiliatedConfederation, UEFA]
-
A.
associatedConfederation
chosen
Indicates a relationship where an entity is linked to, belongs to, or is formally connected with a specific confederation.
-
B.
otherConfederation
Indicates that an entity is associated with a different confederation than another referenced entity, specifying an alternative confederative affiliation or membership.
-
C.
confederation
Indicates a formal union or alliance between multiple entities that retain their individual autonomy while cooperating under a shared framework or agreement.
-
D.
confederation1
Indicates a relationship where multiple entities join together in a loose alliance or union while retaining their individual autonomy.
-
E.
formerConfederation
Indicates that an entity was previously part of a confederation but is no longer a member.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65c2ae94c8190a6a524800686ef66 |
completed | May 2, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:50 a.m.