Triple
T28173682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davenport |
E715530
|
entity |
| Predicate | roadTypeAssociated |
P1019
|
FINISHED |
| Object | early colonial route |
—
|
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: early colonial route | Statement: [Davenport, roadTypeAssociated, early colonial route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTypeAssociated Context triple: [Davenport, roadTypeAssociated, early colonial route]
-
A.
roadAssociatedWith
Indicates that there is a relevant connection or linkage between a road and another entity, such as use, location, function, or impact.
-
B.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
roadTypeAtSquare
Indicates the specific type or classification of road present at a given square or location in a spatial grid or map.
-
D.
roadNumberType
Indicates the classification or type category assigned to a road’s identifying number (e.g., highway, route, local road).
-
E.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 10:14 p.m.