Triple
T36219989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N21 road |
E1047818
|
entity |
| Predicate | hasBypassPlannedAt |
P118215
|
FINISHED |
| Object | Adare |
—
|
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: Adare | Statement: [N21 road, hasBypassPlannedAt, Adare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBypassPlannedAt Context triple: [N21 road, hasBypassPlannedAt, Adare]
-
A.
hasBypass
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
B.
hasBypassProject
chosen
Indicates that an entity is associated with a project designed to bypass, circumvent, or provide an alternative route around something (such as a system, process, or constraint).
-
C.
bypassedSince
Indicates that one entity has been avoided, skipped, or circumvented by another entity starting from a specific point in time and continuing thereafter.
-
D.
isPlannedAround
Indicates that one entity is organized, scheduled, or structured with consideration of, or in alignment with, another entity as a central reference or constraint.
-
E.
isPlannedThrough
Indicates that something is intended to be achieved, organized, or carried out by means of a specified plan, method, or intermediary 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b58004f08190b47d3602e0aa50fb |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.