Triple
T18794048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fossil Room |
E459587
|
entity |
| Predicate | hasDisplayFurniture |
P6895
|
FINISHED |
| Object | 19th-century cabinets |
—
|
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 cabinets | Statement: [Fossil Room, hasDisplayFurniture, 19th-century cabinets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplayFurniture Context triple: [Fossil Room, hasDisplayFurniture, 19th-century cabinets]
-
A.
showsFurniture
Indicates that one entity visually presents or displays furniture items to another entity or audience.
-
B.
containsFurnitureBy
Indicates that one entity includes or holds furniture items that are provided, created, or specified by another entity.
-
C.
furnishingType
chosen
Indicates the type or category of furnishings associated with an entity, such as a property or room.
-
D.
furniture
Indicates that one entity is a piece of furniture associated with, located in, or used by another entity.
-
E.
hasInteriorItem
Indicates that one entity contains another entity as an item located within its interior.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01cc0c0819098ef4326e82ff524 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.