Triple
T13398754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boscoreale |
E319770
|
entity |
| Predicate | museumDisplays |
P32052
|
FINISHED |
| Object | archaeological finds from Boscoreale area |
—
|
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 finds from Boscoreale area | Statement: [Boscoreale, museumDisplays, archaeological finds from Boscoreale area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumDisplays Context triple: [Boscoreale, museumDisplays, archaeological finds from Boscoreale area]
-
A.
museumDisplayType
Indicates the manner or format in which items are presented or exhibited within a museum setting.
-
B.
museumSection
Indicates that one entity is a section, area, or subdivision within a museum associated with the other entity.
-
C.
museumHolds
chosen
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
D.
orientationInMuseum
Indicates the spatial positioning or directional arrangement of an object or exhibit within a museum space.
-
E.
museumFocus
Indicates that a museum is primarily dedicated to or specializes in a particular subject, theme, or type of collection.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d9e7348190844e11dd6cbd13b0 |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.