Triple
T1394749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam Metro line 51 |
E30638
|
entity |
| Predicate | servedFunction |
P4780
|
FINISHED |
| Object | commuter transport |
—
|
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: commuter transport | Statement: [Amsterdam Metro line 51, servedFunction, commuter transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedFunction Context triple: [Amsterdam Metro line 51, servedFunction, commuter transport]
-
A.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
-
C.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
-
D.
assignedFunction
chosen
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c37e60388190a8efcb345be7a1b9 |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.