Triple
T36995085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utrecht rail node |
E915207
|
entity |
| Predicate | hasApproximatePosition |
P22067
|
FINISHED |
| Object | central Netherlands |
—
|
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: central Netherlands | Statement: [Utrecht rail node, hasApproximatePosition, central Netherlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximatePosition Context triple: [Utrecht rail node, hasApproximatePosition, central Netherlands]
-
A.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
B.
hasApproximateLocation
chosen
Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
-
C.
hasApproximateOrigin
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
-
D.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
E.
hasApproximateHeading
Indicates that one entity’s directional heading is approximately the same as another’s, within a specified tolerance.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:14 p.m.