Triple
T8940356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utrecht Chair |
E212883
|
entity |
| Predicate | hasOriginalContext |
P18207
|
FINISHED |
| Object | modern domestic interiors |
—
|
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: modern domestic interiors | Statement: [Utrecht Chair, hasOriginalContext, modern domestic interiors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalContext Context triple: [Utrecht Chair, hasOriginalContext, modern domestic interiors]
-
A.
hasOriginalLocation
Indicates that an entity was initially located or situated at a specified place or position before any change or movement occurred.
-
B.
hasOriginalPrefix
Indicates that an entity retains or is associated with its initial or primary prefix from which later forms or variants are derived.
-
C.
originContext
chosen
Indicates the situational or environmental circumstances from which an entity, event, or piece of information originates.
-
D.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
E.
hasCanonicalContext
Indicates that something is associated with its primary, standard, or officially recognized contextual setting or framework.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b8b37c8190bce6e049de8cf732 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.