Triple
T37898232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Apsley |
E945337
|
entity |
| Predicate | hasConnectionWithRoad |
P51093
|
FINISHED |
| Object | Piccadilly, London |
E10445
|
NE 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: Piccadilly, London | Statement: [Baron Apsley, hasConnectionWithRoad, Piccadilly, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionWithRoad Context triple: [Baron Apsley, hasConnectionWithRoad, Piccadilly, London]
-
A.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
B.
hasRoadConnectionRegion
Indicates that there is a road-based transportation link connecting one region to another.
-
C.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
D.
hasAssociatedRoadSystem
Indicates that one entity is linked to, or served by, a particular road or roadway network.
-
E.
hasRoadway
chosen
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- F. None of above.
Provenance (4 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41043e22a88190ab6aab3ec60808ae |
completed | June 28, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.