Triple
T23703675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAB |
E585659
|
entity |
| Predicate | cityAdministrativeRegion |
P153448
|
FINISHED |
| Object | Canton of Vaud |
—
|
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: Canton of Vaud | Statement: [CAB, cityAdministrativeRegion, Canton of Vaud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityAdministrativeRegion Context triple: [CAB, cityAdministrativeRegion, Canton of Vaud]
-
A.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
B.
cityCouncilRegion
Indicates the administrative region or jurisdiction that a particular city council governs or represents.
-
C.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
D.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
E.
districtAdministration
Indicates that an entity is responsible for managing, governing, or overseeing the administrative affairs of a specific district or local jurisdiction.
- F. None of above. chosen
Provenance (4 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b684e0a88190b7edeb102585ae9d |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f157cc43a881909ed2d8b0a09b5d73 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 17, 2026, 6:53 p.m.