Triple
T36853641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sendai City Museum |
E910734
|
entity |
| Predicate | mainExhibitFocus |
P18644
|
FINISHED |
| Object | Date Masamune |
—
|
NE NERFINISHED |
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: Date Masamune | Statement: [Sendai City Museum, mainExhibitFocus, Date Masamune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainExhibitFocus Context triple: [Sendai City Museum, mainExhibitFocus, Date Masamune]
-
A.
hasExhibitionFocus
Indicates that an exhibition is primarily centered on, or thematically dedicated to, a particular subject, medium, or focus area.
-
B.
museumFocus
chosen
Indicates that a museum is primarily dedicated to or specializes in a particular subject, theme, or type of collection.
-
C.
exhibitFor
Indicates a relationship where something is displayed, presented, or shown for the benefit, use, or consideration of a particular audience, purpose, or entity.
-
D.
exhibitionFeature
Indicates that an exhibition includes or highlights a particular item, work, or element as one of its featured components.
-
E.
exhibitionFunction
Indicates that one entity serves as the function, role, or purpose of an exhibition associated with 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.