Triple
T2833835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONCACAF Women’s Player of the Year |
E62302
|
entity |
| Predicate | votingParticipants |
P2434
|
FINISHED |
| Object | national team coaches |
—
|
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: national team coaches | Statement: [CONCACAF Women’s Player of the Year, votingParticipants, national team coaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingParticipants Context triple: [CONCACAF Women’s Player of the Year, votingParticipants, national team coaches]
-
A.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
B.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
C.
eligibleVoters
Indicates that the referenced entities are legally permitted and qualified to vote in a given election or jurisdiction.
-
D.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
E.
approximateNumberOfVotersBefore
Indicates that one value represents an estimated count of voters that existed prior to a specified point in time or event.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec18b808190aedae2ed11d53b15 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.