Triple
T27222913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 279 in Pennsylvania |
E681327
|
entity |
| Predicate | hasShoulder |
P98301
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Interstate 279 in Pennsylvania, hasShoulder, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShoulder Context triple: [Interstate 279 in Pennsylvania, hasShoulder, yes]
-
A.
hasShoulderButtons
Indicates that an object, typically a device or controller, includes buttons positioned on its shoulders or top side edges.
-
B.
hasShoulderDiameter
Indicates the diameter measurement of an entity’s shoulder region or shoulder-related feature.
-
C.
hasEmergencyShoulder
chosen
Indicates that a roadway segment includes an emergency shoulder area intended for stopped or disabled vehicles.
-
D.
hasShoulderThatIsHighestPointOf
Indicates that an entity’s shoulder is the highest physical point or elevation on that entity.
-
E.
hasShoulderPatchShape
Indicates that one entity possesses a shoulder patch whose form or outline matches the specified shape.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 9:43 a.m.