Triple
T27237910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dax |
E687116
|
entity |
| Predicate | municipalBuilding |
P95689
|
FINISHED |
| Object | Hôtel de Ville de Dax |
—
|
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: Hôtel de Ville de Dax | Statement: [Dax, municipalBuilding, Hôtel de Ville de Dax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalBuilding Context triple: [Dax, municipalBuilding, Hôtel de Ville de Dax]
-
A.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
B.
servesMunicipalBuilding
Indicates that an entity provides services or functions in support of a municipal (city or local government) building.
-
C.
cityHallOf
Indicates that one entity serves as the official city hall building or administrative center for the specified city.
-
D.
capitalBuilding
Indicates that a building serves as the primary governmental or administrative center (capital building) for a political region or entity.
-
E.
hasMunicipalBuildings
chosen
Indicates that a place or jurisdiction possesses one or more buildings used for municipal or local government functions.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 10:34 a.m.