Triple
T21261592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridge Avenue |
E524015
|
entity |
| Predicate | isHistoricRoute |
P12633
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ridge Avenue, isHistoricRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricRoute Context triple: [Ridge Avenue, isHistoricRoute, true]
-
A.
hasHistoricalRoute
chosen
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
-
B.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
isHistoricCrossing
Indicates that a crossing between two locations has historical significance, such as being notable in history, heritage, or past events.
-
D.
isHistoricCourse
Indicates that a course has historical significance, typically due to its age, legacy, or notable past events associated with it.
-
E.
isHistoricCourseAt
Indicates that a course has historically been offered or held at a particular institution or location.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e899e081909d3c98fb12a8b476 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:59 p.m.