Triple
T9611171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgantown History Museum |
E232102
|
entity |
| Predicate | mediaTypeOfContent |
P131
|
FINISHED |
| Object | physical artifacts |
—
|
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: physical artifacts | Statement: [Morgantown History Museum, mediaTypeOfContent, physical artifacts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaTypeOfContent Context triple: [Morgantown History Museum, mediaTypeOfContent, physical artifacts]
-
A.
mediaType
chosen
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
B.
mediaReferenceType
Indicates the specific kind of relationship or role that a referenced media item has in relation to another entity or context.
-
C.
mediaName
Indicates the name or title assigned to a media item (such as a work, file, or publication) in the relationship.
-
D.
mediaTypeOfPresenter
Indicates the type or format of media associated with a given presenter.
-
E.
mediaResponse
Indicates that one entity serves as a reply or reaction in a media format (such as audio, video, or image) to another entity or communication.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a85d4c881909ccab2e972d97e68 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:09 p.m.