Triple
T21987360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magazine Street commercial corridor |
E542997
|
entity |
| Predicate | stretchesFor |
P71793
|
FINISHED |
| Object | several miles |
—
|
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: several miles | Statement: [Magazine Street commercial corridor, stretchesFor, several miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stretchesFor Context triple: [Magazine Street commercial corridor, stretchesFor, several miles]
-
A.
hasLongStretchIn
chosen
Indicates that something extends for a considerable or continuous distance within a specified area, medium, or context.
-
B.
stretchedFrom
Indicates that one entity extends or reaches out in space or time starting at another specified entity or point.
-
C.
isStretchOf
Indicates that one linear feature (such as a road, river, or path) constitutes a continuous segment or portion of another, longer linear feature.
-
D.
frontStretchLength
Indicates the measured length of the front stretch portion of something (such as a track, course, or path).
-
E.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270ad0d48190bd822289ce18195c |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:04 p.m.