Triple
T26776172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Puerto Rican status referendum |
E670124
|
entity |
| Predicate | ballotOption |
P132386
|
FINISHED |
| Object | current territorial status |
—
|
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: current territorial status | Statement: [2017 Puerto Rican status referendum, ballotOption, current territorial status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballotOption Context triple: [2017 Puerto Rican status referendum, ballotOption, current territorial status]
-
A.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
B.
ballotStructure
Indicates how options, candidates, or choices are organized and presented on a ballot for selection.
-
C.
finalBallotCandidate
Indicates that an entity is a candidate who appears on the final ballot in an election or selection process.
-
D.
ballotNumber
Indicates the specific numerical identifier assigned to a ballot within an election or voting process.
-
E.
ballotsInclude
chosen
Indicates that a given set of ballots contains or records the specified option, candidate, or choice.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 4:04 a.m.