Triple
T30826584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 4 |
E785085
|
entity |
| Predicate | isExpresswayIn |
P7229
|
FINISHED |
| Object | parts of San Joaquin County |
—
|
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: parts of San Joaquin County | Statement: [SR 4, isExpresswayIn, parts of San Joaquin County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExpresswayIn Context triple: [SR 4, isExpresswayIn, parts of San Joaquin County]
-
A.
isMotorwayIn
Indicates that a motorway is located within or passes through a specified geographic area or administrative region.
-
B.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
C.
isIntercityHighway
Indicates that a given road segment functions as a highway connecting different cities or urban areas.
-
D.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
-
E.
hasExpresswaySection
chosen
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690f6563c8190afe9208fc511fa43 |
completed | May 3, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.