Triple
T1576845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONCACAF League |
E33671
|
entity |
| Predicate | qualificationSpotAllocation |
P30746
|
FINISHED |
| Object | Central American leagues |
—
|
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: Central American leagues | Statement: [CONCACAF League, qualificationSpotAllocation, Central American leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualificationSpotAllocation Context triple: [CONCACAF League, qualificationSpotAllocation, Central American leagues]
-
A.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
-
B.
arenaLocation
Indicates that an arena is located at or within a specified place or geographic location.
-
C.
inscriptionLocation
Indicates the place or surface on which an inscription is written or engraved.
-
D.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
E.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9607716b4819092187f8c08daaf31 |
completed | March 5, 2026, 10:52 a.m. |
Created at: March 4, 2026, 7:27 p.m.