Triple
T32760480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mojo |
E837739
|
entity |
| Predicate | roadTypeOnCorridor |
P104321
|
FINISHED |
| Object | paved highway |
—
|
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: paved highway | Statement: [Mojo, roadTypeOnCorridor, paved highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTypeOnCorridor Context triple: [Mojo, roadTypeOnCorridor, paved highway]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadTypeAtSquare
Indicates the specific type or classification of road present at a given square or location in a spatial grid or map.
-
C.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
D.
transportationCorridorType
chosen
Indicates the specific kind or classification of a transportation corridor (such as road, rail, or waterway) that characterizes how the route is used for movement or transit.
-
E.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.