Triple
T8078253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Chinese Coin Gallery |
E188547
|
entity |
| Predicate | museumDiscipline |
P18644
|
FINISHED |
| Object | history 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: history museum | Statement: [Ancient Chinese Coin Gallery, museumDiscipline, history museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumDiscipline Context triple: [Ancient Chinese Coin Gallery, museumDiscipline, history museum]
-
A.
museumFocus
chosen
Indicates that a museum is primarily dedicated to or specializes in a particular subject, theme, or type of collection.
-
B.
museumSection
Indicates that one entity is a section, area, or subdivision within a museum associated with the other entity.
-
C.
museumHolds
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
D.
majorMuseum
Indicates that a museum holds significant importance or prominence, typically due to its size, collections, reputation, or cultural impact.
-
E.
purposeOfMuseum
Indicates that a specified purpose or function is attributed to 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a2b64c8190ae2b3414b4f840e4 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.