Triple
T16771992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woerden–Leiden railway |
E407619
|
entity |
| Predicate | hasIntermediateStopsIn |
P24279
|
FINISHED |
| Object | towns in South Holland |
—
|
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: towns in South Holland | Statement: [Woerden–Leiden railway, hasIntermediateStopsIn, towns in South Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntermediateStopsIn Context triple: [Woerden–Leiden railway, hasIntermediateStopsIn, towns in South Holland]
-
A.
hasIntermediateStation
Indicates that a route, journey, or connection includes a station that lies between its starting point and its final destination.
-
B.
numberOfIntermediateStops
Indicates the count of stops or pauses that occur between the starting point and the final destination in a journey or process.
-
C.
hasIntermediateCity
chosen
Indicates that there is a city located between two other places along a route or connection.
-
D.
intermediateOriginOnFinalItinerary
Indicates that an entity serves as a non-final (intermediate) stop or origin point along a complete, final travel itinerary.
-
E.
hasIntermediate
Indicates that there exists one or more entities that serve as a middle or transitional step between two related entities or stages.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b036ff788190bd9f166c3f127818 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.