Triple
T11722060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boot Flake |
E278659
|
entity |
| Predicate | routeSectionOf |
P21871
|
FINISHED |
| Object | The Nose standard line |
—
|
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: The Nose standard line | Statement: [Boot Flake, routeSectionOf, The Nose standard line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeSectionOf Context triple: [Boot Flake, routeSectionOf, The Nose standard line]
-
A.
streetSectionOf
Indicates that one street segment or portion belongs to, is contained within, or forms part of a larger street or roadway.
-
B.
routeSegment
chosen
Indicates a specific portion of a larger route that directly connects two points or locations within that route.
-
C.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
D.
routeDescription
Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
-
E.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c373088190bc2ae77a1696d280 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.