Triple
T17694251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Post Road |
E441118
|
entity |
| Predicate | originalSurface |
P32808
|
FINISHED |
| Object | dirt road |
—
|
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: dirt road | Statement: [Boston Post Road, originalSurface, dirt road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSurface Context triple: [Boston Post Road, originalSurface, dirt road]
-
A.
formerSurface
chosen
Indicates that one entity previously served as the surface or outer layer of another entity, but no longer does so.
-
B.
secondarySurface
Indicates a relationship where one surface functions as a secondary or subordinate surface in relation to a primary or main surface.
-
C.
originalSide
Indicates that an entity remains on or is associated with its initial or starting side in a given context or relationship.
-
D.
laterSurface
Indicates that one surface or layer occurs or appears at a later time than another surface or layer in a sequence or process.
-
E.
outerSurface
Indicates that one entity forms the external boundary or outermost layer of another entity.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715485d88190b9b6f347ff85d7c7 |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:04 a.m.