Triple
T27313289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A18 motorway (Netherlands) |
E689265
|
entity |
| Predicate | hasAccessToTown |
P170375
|
FINISHED |
| Object | Doetinchem |
—
|
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: Doetinchem | Statement: [A18 motorway (Netherlands), hasAccessToTown, Doetinchem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessToTown Context triple: [A18 motorway (Netherlands), hasAccessToTown, Doetinchem]
-
A.
hasVillageAccess
Indicates that an entity is permitted to enter, use, or benefit from the facilities, services, or areas of a particular village.
-
B.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
C.
hasTownStatus
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
-
D.
hasCityRight
Indicates that an entity possesses legal or official rights associated with a particular city, such as jurisdiction, privileges, or authority within that city.
-
E.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 11:29 a.m.