Triple
T18743161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia State Colony for Epileptics and Feeble-Minded |
E458339
|
entity |
| Predicate | BuckV.BellDecisionYear |
P2233
|
FINISHED |
| Object | 1927 |
—
|
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: 1927 | Statement: [Virginia State Colony for Epileptics and Feeble-Minded, BuckV.BellDecisionYear, 1927]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BuckV.BellDecisionYear Context triple: [Virginia State Colony for Epileptics and Feeble-Minded, BuckV.BellDecisionYear, 1927]
-
A.
yearDecided
chosen
Indicates the specific calendar year in which a decision, ruling, or resolution was formally made or finalized.
-
B.
HallOfFameBallots
Indicates that there exists a set of official votes or selections cast to determine induction into a hall of fame.
-
C.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
D.
hasDecisionMaker
Indicates that one entity serves as the decision-making authority or agent for another entity.
-
E.
MVPDecision
Indicates a decision-making relationship where an entity is selected or judged as the Most Valuable Player (MVP) among a set of candidates.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e57690a4d081908ab4c3890bb07e86 |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.