Triple
T16936359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall of Emperors |
E410836
|
entity |
| Predicate | museumTypeContext |
P7675
|
FINISHED |
| Object | archaeological museum gallery |
—
|
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: archaeological museum gallery | Statement: [Hall of Emperors, museumTypeContext, archaeological museum gallery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumTypeContext Context triple: [Hall of Emperors, museumTypeContext, archaeological museum gallery]
-
A.
museumDisplayType
Indicates the manner or format in which items are presented or exhibited within a museum setting.
-
B.
hasMuseumType
chosen
Indicates that an entity is classified as a museum of a specific type or category.
-
C.
museumInventoryType
Indicates the type or category under which an item is classified within a museum’s inventory system.
-
D.
museumFocus
Indicates that a museum is primarily dedicated to or specializes in a particular subject, theme, or type of collection.
-
E.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2a05f48190a0a8ac86985f4000 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.