Triple
T34465453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N81 road |
E884755
|
entity |
| Predicate | runsThroughTown |
P27125
|
FINISHED |
| Object | Tallaght |
—
|
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: Tallaght | Statement: [N81 road, runsThroughTown, Tallaght]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsThroughTown Context triple: [N81 road, runsThroughTown, Tallaght]
-
A.
flowsThroughTown
Indicates that something, typically a river or stream, passes through the area or boundaries of a town.
-
B.
runsThroughNeighborhood
chosen
Indicates that something (such as a route, path, or service) passes through or traverses a particular neighborhood.
-
C.
runsAround
Indicates that one entity moves in a circular or surrounding path around another entity or area.
-
D.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
E.
runsInto
Indicates that one entity moves so as to collide or come into sudden contact with another entity.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71999aec481908c81bc0a9250d7fb |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2:01 a.m.