Triple
T29478125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONCACAF Competitions Committee |
E747705
|
entity |
| Predicate | subjectToStatutesOf |
P93043
|
FINISHED |
| Object | CONCACAF |
—
|
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: CONCACAF | Statement: [CONCACAF Competitions Committee, subjectToStatutesOf, CONCACAF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToStatutesOf Context triple: [CONCACAF Competitions Committee, subjectToStatutesOf, CONCACAF]
-
A.
hasStatutes
chosen
Indicates that one entity possesses, is governed by, or is associated with a set of formal laws or statutes defined by another entity.
-
B.
hasStatuteLaw
Indicates that a jurisdiction or entity is governed by, or possesses, a body of formal written laws enacted by a legislative authority.
-
C.
establishedByStatute
Indicates that something has been formally created, defined, or authorized through a specific law or statute.
-
D.
modifiedByStatute
Indicates that a legal provision, rule, or document has been changed, amended, or otherwise altered by a specific statute.
-
E.
affectsStatute
Indicates that one legal action, decision, or document has a modifying, influencing, or changing impact on a particular statute.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 4:01 p.m.