Triple
T30658420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 107 |
E780453
|
entity |
| Predicate | primaryStreetName |
P5943
|
FINISHED |
| Object | Hawthorne Boulevard |
E2286643
|
NE 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: Hawthorne Boulevard | Statement: [California State Route 107, primaryStreetName, Hawthorne Boulevard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStreetName Context triple: [California State Route 107, primaryStreetName, Hawthorne Boulevard]
-
A.
mainStraightName
Indicates the name assigned to the primary straight segment or main straight portion of something (such as a route, track, or road).
-
B.
previousStreetName
Indicates that one street name was formerly used for a street that now has a different, current name.
-
C.
namedAfterStreet
Indicates that an entity’s name is derived from or taken in honor of a particular street.
-
D.
primaryStreetAlignment
Indicates that two or more primary streets share the same or a specified relative directional orientation or alignment.
-
E.
roadName
chosen
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
- F. None of above.
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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0317eaf4e88190a6f6419cb4ef7547 |
completed | May 12, 2026, 12:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a7c453326148190a583b01a83479d7b |
completed | Aug. 12, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_6a03179da394819095e3d346c3785d74 |
completed | May 12, 2026, 12:05 p.m. |
Created at: April 29, 2026, 8:30 p.m.