Triple
T27606607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern California car culture |
E700196
|
entity |
| Predicate | hasIconicCruisingStrip |
P163297
|
FINISHED |
| Object | Whittier Boulevard |
—
|
NE NERFINISHED |
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: Whittier Boulevard | Statement: [Southern California car culture, hasIconicCruisingStrip, Whittier Boulevard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconicCruisingStrip Context triple: [Southern California car culture, hasIconicCruisingStrip, Whittier Boulevard]
-
A.
hasCommercialStrip
Indicates that an area or entity contains or is associated with a zone characterized by a concentration of commercial businesses or retail establishments.
-
B.
hasCruiseTraffic
Indicates that there is cruise ship traffic occurring at or involving a particular location or route.
-
C.
hasDragStrip
Indicates that one entity includes, contains, or is equipped with a drag strip used for drag racing.
-
D.
hasIconicPlay
Indicates that an entity is associated with a particularly famous, defining, or emblematic play or performance.
-
E.
hasDistinctiveEmblem
Indicates that an entity possesses a unique symbol, logo, or emblem that serves to distinguish it from others.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 2:10 p.m.