Triple
T503294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piccadilly |
E10445
|
entity |
| Predicate | passesAlong |
P11198
|
FINISHED |
| Object | northern boundary of Green Park |
—
|
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: northern boundary of Green Park | Statement: [Piccadilly, passesAlong, northern boundary of Green Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesAlong Context triple: [Piccadilly, passesAlong, northern boundary of Green Park]
-
A.
isPassedThroughBy
chosen
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
B.
passes
Indicates that one entity successfully transfers, hands over, or moves something (such as an object, message, or responsibility) to another entity.
-
C.
passesCity
Indicates that a route, path, or journey goes through or traverses a particular city as part of its course.
-
D.
passesThroughCountry
Indicates that a route, path, or object traverses or crosses within the boundaries of a specified country.
-
E.
passesThroughFacility
Indicates that something (such as a person, object, or shipment) moves through or is routed via a particular facility as part of its path or process.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1357738819085eae6c10fa2fca9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.