Triple
T19105956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Group of the Year |
E467654
|
entity |
| Predicate | votingBodyIncludes |
P103087
|
FINISHED |
| Object | record labels |
—
|
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: record labels | Statement: [International Group of the Year, votingBodyIncludes, record labels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingBodyIncludes Context triple: [International Group of the Year, votingBodyIncludes, record labels]
-
A.
usesVotingBody
Indicates that one entity employs or relies on a particular voting body to make decisions or take actions on its behalf.
-
B.
ballotsInclude
Indicates that a given set of ballots contains or records the specified option, candidate, or choice.
-
C.
governingBodyIncludes
chosen
Indicates that a governing body has a particular entity as one of its members or constituent parts.
-
D.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
E.
includesElectionsIn
Indicates that one entity (such as a document, dataset, or process) encompasses, covers, or contains elections that occur within the scope or domain of another entity.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e37159688190a6896d9730214ba8 |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.