Triple
T2030250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels Park |
E44498
|
entity |
| Predicate | hasPlanningStyle |
P34728
|
FINISHED |
| Object | neoclassical urban design |
—
|
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: neoclassical urban design | Statement: [Brussels Park, hasPlanningStyle, neoclassical urban design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningStyle Context triple: [Brussels Park, hasPlanningStyle, neoclassical urban design]
-
A.
hasPlanningCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
-
B.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
C.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
D.
hasDecisionMakingStyle
Indicates that an entity possesses or exhibits a particular way or pattern of making decisions.
-
E.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb914a40081909a937689bea3dc85 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:38 p.m.