Triple
T4313474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Choice Award |
E94130
|
entity |
| Predicate | hasVotingGroup |
P38956
|
FINISHED |
| Object | festival attendees |
—
|
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: festival attendees | Statement: [People’s Choice Award, hasVotingGroup, festival attendees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingGroup Context triple: [People’s Choice Award, hasVotingGroup, festival attendees]
-
A.
hasVotingMembers
Indicates that certain entities are recognized as having individuals or units with the authority to vote within a group, body, or decision-making process.
-
B.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
C.
hasNumberOfVotingMembers
Indicates the specific count of individuals who hold voting rights within a given group or body.
-
D.
hasTypeOfVoters
chosen
Indicates that an entity is associated with or characterized by a particular category or kind of voters.
-
E.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350f319c08190bb40a9fc5933728d |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.