Triple
T15049031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serenbe |
E379304
|
entity |
| Predicate | transportationDesign |
P116535
|
FINISHED |
| Object | pedestrian-oriented |
—
|
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: pedestrian-oriented | Statement: [Serenbe, transportationDesign, pedestrian-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationDesign Context triple: [Serenbe, transportationDesign, pedestrian-oriented]
-
A.
transportModeDesigned
Indicates that one entity is a mode of transport specifically designed or intended for use by another entity.
-
B.
transportation
Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
-
C.
showsTransportation
Indicates that one entity presents or depicts a means or mode of transportation associated with another entity.
-
D.
transportTechnology
Indicates a relationship where one entity serves as the means, system, or method used to transport or move another entity from one place to another.
-
E.
transports
Indicates that one entity carries or conveys another entity from one place to another.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda8f71988190b4fe7f7de4ccb798 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 3 a.m.