Triple
T6007241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castro Street, Mountain View |
E133740
|
entity |
| Predicate | pedestrianOrientation |
P68715
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Castro Street, Mountain View, pedestrianOrientation, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianOrientation Context triple: [Castro Street, Mountain View, pedestrianOrientation, high]
-
A.
pedestrianActivity
Indicates that an entity is engaged in or associated with walking or other on-foot movement or behavior.
-
B.
pedestrianFriendly
Indicates that an environment, route, or area is designed or suitable for safe, comfortable, and convenient use by pedestrians.
-
C.
hasPedestrianPriority
Indicates that pedestrians are given precedence or right-of-way over other road users in a particular context or area.
-
D.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
E.
pedestrianOnly
Indicates that a path, area, or route is designated exclusively for pedestrians and prohibits vehicle access.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f13d9908190a11d9bef8652db93 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:06 p.m.