Triple
T11728526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR |
E278838
|
entity |
| Predicate | partOfNotation |
P95660
|
FINISHED |
| Object | California State Route numbering system |
—
|
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: California State Route numbering system | Statement: [SR, partOfNotation, California State Route numbering system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfNotation Context triple: [SR, partOfNotation, California State Route numbering system]
-
A.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
B.
distinguishingNotation
Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
-
C.
partOfMusical
Indicates that something is a component, segment, or element belonging to a larger musical work or performance.
-
D.
usesNotationFor
chosen
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
-
E.
musicalSymbol
Indicates that one entity is a musical notation mark or sign associated with another entity in a musical context.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d80ef881908cab956787ab07fd |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.