Triple
T24762630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Historic Parkway |
E619488
|
entity |
| Predicate | hasOfficialNameContaining |
P158107
|
FINISHED |
| Object | Historic Parkway |
—
|
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: Historic Parkway | Statement: [California Historic Parkway, hasOfficialNameContaining, Historic Parkway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialNameContaining Context triple: [California Historic Parkway, hasOfficialNameContaining, Historic Parkway]
-
A.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
B.
refersToOfficialName
Indicates that one entity is referencing or using the formally recognized, official name of another entity.
-
C.
hasOfficialDualNameWith
Indicates that two entities share an officially recognized dual or joint name used in formal contexts.
-
D.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
-
E.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 4:27 a.m.