Triple
T35290412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam (via Uithoorn) |
E1019205
|
entity |
| Predicate | impliesStopover |
P138842
|
FINISHED |
| Object | Uithoorn |
—
|
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: Uithoorn | Statement: [Amsterdam (via Uithoorn), impliesStopover, Uithoorn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesStopover Context triple: [Amsterdam (via Uithoorn), impliesStopover, Uithoorn]
-
A.
isStopoverPoint
Indicates that a location serves as an intermediate stopping point along a journey or route, rather than the final destination.
-
B.
hasStopoverState
Indicates that an entity’s journey or process includes an intermediate stop or temporary state before reaching its final destination or outcome.
-
C.
stopoverAirport
Indicates that an itinerary or flight includes a particular airport as an intermediate stop between the origin and final destination.
-
D.
stopoverLocation
chosen
Indicates that an entity makes an intermediate stop or layover at a specified location during a journey or route.
-
E.
aircraftStopover
Indicates that an aircraft makes an intermediate stop at a specific location during its journey between origin and final destination.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79013a2308190a13818632a697230 |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.