Triple
T15520238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Museum of Ireland – Archaeology |
E368943
|
entity |
| Predicate | collectionHighlight |
P101209
|
FINISHED |
| Object | Treasury exhibition |
—
|
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: Treasury exhibition | Statement: [National Museum of Ireland – Archaeology, collectionHighlight, Treasury exhibition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionHighlight Context triple: [National Museum of Ireland – Archaeology, collectionHighlight, Treasury exhibition]
-
A.
highlights
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
B.
themeHighlights
Indicates that certain elements are emphasized or visually distinguished as key features within a particular theme.
-
C.
highlightsSign
Indicates that one entity visually emphasizes or draws special attention to a sign.
-
D.
collectionFeature
Indicates that a collection possesses or is characterized by a particular feature or attribute.
-
E.
featuredFor
chosen
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e040343d9c8190a7d1f197c108bd9d |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:04 a.m.