Triple
T24352276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 134 |
E613823
|
entity |
| Predicate | isAmbiguousTitleFor |
P71696
|
FINISHED |
| Object | multiple state highways in different states |
—
|
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: multiple state highways in different states | Statement: [SR 134, isAmbiguousTitleFor, multiple state highways in different states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAmbiguousTitleFor Context triple: [SR 134, isAmbiguousTitleFor, multiple state highways in different states]
-
A.
isAmbiguousName
chosen
Indicates that a name can refer to multiple distinct entities or interpretations, making its reference unclear without additional context.
-
B.
isTitleFor
Indicates that one entity serves as the official title or name designation for another entity.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
E.
hasAmbiguous
Indicates that the relationship or state is unclear, uncertain, or open to multiple interpretations.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293467a508190937b9614870e243e |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:59 a.m.