Triple
T3825945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tram line 7 (VBZ) |
E88689
|
entity |
| Predicate | municipalService |
P6352
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tram line 7 (VBZ), municipalService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalService Context triple: [Tram line 7 (VBZ), municipalService, yes]
-
A.
hasMunicipalService
chosen
Indicates that a municipality provides or is responsible for a specific public service to a given area, facility, or population.
-
B.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
-
C.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
D.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
E.
hasMunicipalServiceProvider
Indicates that a municipality is served by a specific organization or entity that provides municipal services (such as utilities, waste management, or public transport).
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8459f881908a2c91bb07e381ef |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.