Triple
T8391469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue de Maubeuge |
E197951
|
entity |
| Predicate | hasCityPlanningPeriod |
P61342
|
FINISHED |
| Object | 19th century Paris urban renewal |
—
|
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: 19th century Paris urban renewal | Statement: [Rue de Maubeuge, hasCityPlanningPeriod, 19th century Paris urban renewal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityPlanningPeriod Context triple: [Rue de Maubeuge, hasCityPlanningPeriod, 19th century Paris urban renewal]
-
A.
hasUrbanPlanning
chosen
Indicates that an entity is involved in, responsible for, or characterized by activities or attributes related to urban planning.
-
B.
isPlannedCity
Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
-
C.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
D.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
E.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb810e16b081908e2c25bfb9d590ed |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.