Triple
T30577875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A4 road (London) traffic route |
E778298
|
entity |
| Predicate | runsWestFrom |
P169869
|
FINISHED |
| Object | central London |
—
|
NE NERFINISHED |
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: central London | Statement: [A4 road (London) traffic route, runsWestFrom, central London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsWestFrom Context triple: [A4 road (London) traffic route, runsWestFrom, central London]
-
A.
runsSouthFrom
Indicates that one entity extends or moves in a generally southward direction starting from the location of another entity.
-
B.
westStartingForward
Indicates that an entity serves as the starting forward player for a team or lineup associated with the west (e.g., a western conference, division, or region).
-
C.
startingForwardWest
Indicates that an entity begins moving or facing in the forward direction toward the west.
-
D.
locatedWestOf
Indicates that one entity is positioned geographically to the west of another entity.
-
E.
flowsWestFrom
Indicates that something (typically a fluid or current) moves in a westward direction starting from a specified source or location.
- F. None of above. chosen
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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6893ee6a081908d04f81d92a0c210 |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:23 p.m.