Triple
T21981832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Misery |
E542857
|
entity |
| Predicate | hasExhibitRole |
P129897
|
FINISHED |
| Object | outdoor museum building |
—
|
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: outdoor museum building | Statement: [Fort Misery, hasExhibitRole, outdoor museum building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitRole Context triple: [Fort Misery, hasExhibitRole, outdoor museum building]
-
A.
hasExhibitionFunction
chosen
Indicates that an entity serves the role or purpose of exhibiting, displaying, or presenting something (e.g., objects, works, or information).
-
B.
canExhibit
Indicates that one entity has the ability or potential to display, manifest, or show a particular property, behavior, or characteristic.
-
C.
hasCuratorialRole
Indicates that an entity holds a curatorial position or responsibility in relation to another entity, such as overseeing its selection, organization, or presentation.
-
D.
hasExhibitionScope
Indicates the thematic, geographic, temporal, or conceptual range and boundaries that define what an exhibition covers.
-
E.
hasExhibition
Indicates that an entity organizes, hosts, or presents a particular exhibition.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248de3688190a8d24cc8458851f2 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:04 p.m.