Triple
T22728637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durbar Hall |
E562064
|
entity |
| Predicate | interiorDesignInfluence |
P16767
|
FINISHED |
| Object | European royal courts |
—
|
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: European royal courts | Statement: [Durbar Hall, interiorDesignInfluence, European royal courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorDesignInfluence Context triple: [Durbar Hall, interiorDesignInfluence, European royal courts]
-
A.
designInfluenceOn
Indicates that one design, designer, or design-related factor has an effect on shaping, guiding, or altering another design or design outcome.
-
B.
architecturalInfluence
chosen
Indicates that one architectural style, structure, or designer has had a formative impact on the design, style, or features of another.
-
C.
partOfInteriorDesign
Indicates that one entity is a component or element within the interior design scheme of another entity.
-
D.
interiorStyle
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
E.
interiorDecoratedBy
Indicates that the interior of a space or structure has been designed or decorated by a specific agent or entity.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792b22cc819099aa00bb2dbacce3 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:21 p.m.