Triple
T12567499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connaught Road Central |
E295508
|
entity |
| Predicate | isCoastalRoadHistorically |
P29483
|
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: [Connaught Road Central, isCoastalRoadHistorically, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalRoadHistorically Context triple: [Connaught Road Central, isCoastalRoadHistorically, true]
-
A.
isCoastalTrail
Indicates that a trail is located along or near a coastline, typically following or closely paralleling the shore.
-
B.
historicRoute
chosen
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
C.
isScenicByway
Indicates that a roadway is officially designated as a scenic byway, recognized for its notable visual, cultural, or natural appeal along its route.
-
D.
isHistoricCoastalCity
Indicates that a city is both historically significant and located along a coast.
-
E.
hasHistoricStreet
Indicates that an entity is associated with or located on a street that has recognized historical significance.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:49 p.m.