Triple
T38485678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mile Road System (Detroit) |
E917908
|
entity |
| Predicate | distanceReferencePoint |
P140307
|
FINISHED |
| Object | Downtown Detroit |
E162397
|
NE 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: Downtown Detroit | Statement: [Mile Road System (Detroit), distanceReferencePoint, Downtown Detroit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceReferencePoint Context triple: [Mile Road System (Detroit), distanceReferencePoint, Downtown Detroit]
-
A.
distanceReferenceGroup
Indicates a relationship where one entity serves as the reference group from which the distance to another entity is measured or evaluated.
-
B.
hasDistanceReference
chosen
Indicates that a distance value is specified relative to a particular reference point, scale, or standard.
-
C.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
D.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
E.
distance
Indicates the spatial separation or length between two points, objects, or locations.
- F. None of above.
Provenance (4 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ccc6187881908da45619d521ca28 |
completed | June 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.