Triple
T7498999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONCACAF Player of the Century (fan vote) |
E177210
|
entity |
| Predicate | votingScope |
P77868
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [CONCACAF Player of the Century (fan vote), votingScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingScope Context triple: [CONCACAF Player of the Century (fan vote), votingScope, international]
-
A.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
B.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
C.
vetoScope
Indicates that one party has the authority to reject or block certain decisions, actions, or proposals within a defined domain or set of matters.
-
D.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
E.
votingUnit
Indicates a relationship where an entity functions as a unit or body that casts votes or participates in a voting process.
- 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_69c69f2696688190915a8458f2398211 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:44 p.m.