Triple
T28077887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saar Statute |
E709594
|
entity |
| Predicate | cameToPublicVoteOn |
P164023
|
FINISHED |
| Object | 23 October 1955 |
—
|
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: 23 October 1955 | Statement: [Saar Statute, cameToPublicVoteOn, 23 October 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameToPublicVoteOn Context triple: [Saar Statute, cameToPublicVoteOn, 23 October 1955]
-
A.
hasPublicVoting
Indicates that decisions, selections, or evaluations are made through a voting process that is open and accessible to the general public.
-
B.
castingVote
Indicates that an entity formally expresses a decisive choice or preference in a vote, often determining the outcome.
-
C.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
D.
voted
Indicates that an entity formally expressed a choice or decision, typically in an election, poll, or decision-making process, regarding another entity or option.
-
E.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 8:50 p.m.