Triple
T11101845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus street lighting arches |
E262526
|
entity |
| Predicate | spanned |
P44555
|
FINISHED |
| Object | downtown Columbus streets |
—
|
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: downtown Columbus streets | Statement: [Columbus street lighting arches, spanned, downtown Columbus streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spanned Context triple: [Columbus street lighting arches, spanned, downtown Columbus streets]
-
A.
baySpanned
Indicates that a structure or feature extends across and covers the width of a bay.
-
B.
expandedAcross
Indicates that something has grown or extended so that it now spans or covers multiple areas, regions, or segments.
-
C.
spanType
Indicates the specific category or kind of span that characterizes the relationship or action between entities.
-
D.
isSpanning
chosen
Indicates that one entity extends across, covers, or bridges the full width, extent, or duration of another entity.
-
E.
leafSpan
Indicates the extent or range covered by a leaf, such as its length, width, or overall spread.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2ab09081908ffce2df8912b657 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.