Triple
T17931150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Years Gallery |
E448334
|
entity |
| Predicate | museumSector |
P15855
|
FINISHED |
| Object | military museum |
—
|
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: military museum | Statement: [Early Years Gallery, museumSector, military museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumSector Context triple: [Early Years Gallery, museumSector, military museum]
-
A.
museumSection
chosen
Indicates that one entity is a section, area, or subdivision within a museum associated with the other entity.
-
B.
museumFocus
Indicates that a museum is primarily dedicated to or specializes in a particular subject, theme, or type of collection.
-
C.
majorMuseum
Indicates that a museum holds significant importance or prominence, typically due to its size, collections, reputation, or cultural impact.
-
D.
museumOrSite
Indicates that one entity is a museum or cultural/historical site associated with or relevant to another entity.
-
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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a551e1788190abad0d6a85ec55e1 |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.