Triple
T19558994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulevard Pereire |
E489391
|
entity |
| Predicate | urbanStyle |
P121907
|
FINISHED |
| Object | Haussmannian urban planning |
—
|
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: Haussmannian urban planning | Statement: [Boulevard Pereire, urbanStyle, Haussmannian urban planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanStyle Context triple: [Boulevard Pereire, urbanStyle, Haussmannian urban planning]
-
A.
nationalStyle
Indicates that something is characterized by or associated with the distinctive style of a particular nation.
-
B.
rumStyle
Indicates the stylistic category or production tradition that characterizes a given rum.
-
C.
inTheStyleOf
chosen
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
D.
fashionStyle
Indicates the characteristic way in which an entity dresses or presents themselves in terms of clothing and appearance.
-
E.
governsInStyle
Indicates that a governing entity exercises authority or leadership in a distinctive, notable, or characteristic manner.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f723d5081909553a4363b579a6b |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.