Triple
T24466678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotterdam tram network |
E616988
|
entity |
| Predicate | hasOperatorHeadquarters |
P95731
|
FINISHED |
| Object | Rotterdam |
—
|
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: Rotterdam | Statement: [Rotterdam tram network, hasOperatorHeadquarters, Rotterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatorHeadquarters Context triple: [Rotterdam tram network, hasOperatorHeadquarters, Rotterdam]
-
A.
hasOperatorHeadquartersIn
chosen
Indicates that the primary operational headquarters of an operator is located in a specified place.
-
B.
hasOrganizationHeadquarters
Indicates that an organization’s main administrative or operational center is located at a specific place.
-
C.
hasHeadquartersFunctionFor
Indicates that an entity serves as the central coordinating or managing headquarters for another entity’s operations or activities.
-
D.
hasHeadquartersType
Indicates the specific kind or classification of headquarters associated with an entity.
-
E.
hasManufacturerHeadquartersIn
Indicates that the location specified is the place where the manufacturer’s main headquarters is situated.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299403a8c819095e31aa2dace6921 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.