Triple
T6835337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leidsevaart |
E157434
|
entity |
| Predicate | wasServedBy |
P19592
|
FINISHED |
| Object | trekschuit service between Haarlem and Leiden |
—
|
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: trekschuit service between Haarlem and Leiden | Statement: [Leidsevaart, wasServedBy, trekschuit service between Haarlem and Leiden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasServedBy Context triple: [Leidsevaart, wasServedBy, trekschuit service between Haarlem and Leiden]
-
A.
presentlyServedBy
Indicates that an entity is currently being provided with service or attended to by another entity.
-
B.
crewServed
Indicates that the operation or use of something requires a coordinated effort by multiple people acting together as a crew.
-
C.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
D.
historicallyServedBy
chosen
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67a9ff88190b0d86331b3ea06aa |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.