Triple
T19911212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesa Southwest Museum |
E478550
|
entity |
| Predicate | hasDinosaurExhibit |
P22362
|
FINISHED |
| Object | indoor dinosaur mountain display |
—
|
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: indoor dinosaur mountain display | Statement: [Mesa Southwest Museum, hasDinosaurExhibit, indoor dinosaur mountain display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDinosaurExhibit Context triple: [Mesa Southwest Museum, hasDinosaurExhibit, indoor dinosaur mountain display]
-
A.
hasDinosaurMuseum
Indicates that a place or entity possesses or hosts a museum dedicated primarily to dinosaurs.
-
B.
hasExhibitSpecies
chosen
Indicates that an exhibit or display includes or features a particular species.
-
C.
hasAssociatedAnimalExhibit
Indicates that an entity is linked to a specific animal exhibit that is related or relevant to it.
-
D.
hasExhibits
Indicates that an entity (such as a museum, gallery, or event) displays or presents certain items, artworks, or objects as part of its collection or show.
-
E.
hasIndoorExhibits
Indicates that an entity provides or contains exhibits that are located indoors.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6598f31c481908a5a1d9a5656f698 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.