Triple
T23203237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSF |
E580374
|
entity |
| Predicate | UEFAmembershipStatus |
P45472
|
FINISHED |
| Object | full member |
—
|
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: full member | Statement: [FSF, UEFAmembershipStatus, full member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UEFAmembershipStatus Context triple: [FSF, UEFAmembershipStatus, full member]
-
A.
uefaOfficialStatus
Indicates that an entity holds an official status or recognition granted by UEFA (the Union of European Football Associations).
-
B.
uefaAffiliation
chosen
Indicates that an entity is officially affiliated with, recognized by, or a member of UEFA (the Union of European Football Associations).
-
C.
affiliationDateToUEFA
Indicates the date on which an entity formally became affiliated with UEFA.
-
D.
EUMemberSince
Indicates the point in time from which an entity has been a member of the European Union.
-
E.
hasEuropeanUnionMembershipThrough
Indicates that an entity holds membership in the European Union indirectly or by virtue of another entity (such as a state, territory, or organization) through which that membership is conferred.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907a8bb48190846802a24d33bccf |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.