Triple
T32260630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place de la Brèche |
E824141
|
entity |
| Predicate | isMajorUrbanSpaceOf |
P164996
|
FINISHED |
| Object | Niort city centre |
—
|
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: Niort city centre | Statement: [Place de la Brèche, isMajorUrbanSpaceOf, Niort city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorUrbanSpaceOf Context triple: [Place de la Brèche, isMajorUrbanSpaceOf, Niort city centre]
-
A.
isUrbanSectionOf
Indicates that one area or segment is the part of a larger entity that lies within an urban or city environment.
-
B.
isUrbanBackdropOf
Indicates that one entity serves as the city or metropolitan background setting against which another entity is situated, depicted, or occurs.
-
C.
isMajorPublicSpaceOf
chosen
Indicates that a location functions as a primary, widely accessible public area within or associated with another place or entity.
-
D.
isUrbanCenter
Indicates that a place functions as a primary, densely developed hub of population, services, and activities within a region.
-
E.
isUrbanAreaOn
Indicates that an urban area is geographically situated on or directly above a specified physical feature, surface, or region.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 12:41 a.m.