Triple
T21968139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA U-23 World Cup |
E542511
|
entity |
| Predicate | conceptStatus |
P64266
|
FINISHED |
| Object | proposed |
—
|
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: proposed | Statement: [FIFA U-23 World Cup, conceptStatus, proposed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptStatus Context triple: [FIFA U-23 World Cup, conceptStatus, proposed]
-
A.
hasConceptualStatus
Indicates that an entity holds a particular abstract, theoretical, or conceptual standing or classification within a given framework or context.
-
B.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
C.
ontologyStatus
chosen
Indicates the current state or condition of an entity within an ontology lifecycle (e.g., proposed, active, deprecated, or obsolete).
-
D.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
E.
canonicalStatusIn
Indicates that something has a particular canonical or officially recognized status within a specified context or system.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1245c5d148190af2a06190ba32feb |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:02 p.m.