Triple
T4601497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodeo Drive |
E100328
|
entity |
| Predicate | famousSectionLength |
P266
|
FINISHED |
| Object | approximately 3 blocks |
—
|
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: approximately 3 blocks | Statement: [Rodeo Drive, famousSectionLength, approximately 3 blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousSectionLength Context triple: [Rodeo Drive, famousSectionLength, approximately 3 blocks]
-
A.
notableSection
Indicates that a particular part or segment of something is especially important, prominent, or worthy of attention within the whole.
-
B.
famousRoute
Indicates that a route is widely known or celebrated, typically due to its historical, cultural, or touristic significance.
-
C.
famousVariant
Indicates that one entity is a well-known or widely recognized version or form of another entity.
-
D.
notableSectionNear
Indicates that one section or segment is located physically close to another section or segment in a way that is noteworthy or significant.
-
E.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd597346a08190b47eda3b73076f8b |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.