Triple
T34115193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoder, Kansas |
E874951
|
entity |
| Predicate | roadSignWarning |
P8566
|
FINISHED |
| Object | horse-drawn vehicles |
—
|
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: horse-drawn vehicles | Statement: [Yoder, Kansas, roadSignWarning, horse-drawn vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSignWarning Context triple: [Yoder, Kansas, roadSignWarning, horse-drawn vehicles]
-
A.
roadSignageIndicates
chosen
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
-
B.
roadSignPrefix
Indicates a relationship where one element serves as the initial or leading part of a road sign’s text, code, or designation.
-
C.
roadSignCode
Indicates the specific regulatory or informational code assigned to a road sign that defines its meaning or instruction.
-
D.
warningSignShape
Indicates the geometric form or outline that a warning sign is designed or depicted to have.
-
E.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb880008190bc1ca79d89580949 |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.