Triple
T12941589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six Gallery reading |
E309648
|
entity |
| Predicate | mediaTypeDocumentedIn |
P131
|
FINISHED |
| Object | memoir |
—
|
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: memoir | Statement: [Six Gallery reading, mediaTypeDocumentedIn, memoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaTypeDocumentedIn Context triple: [Six Gallery reading, mediaTypeDocumentedIn, memoir]
-
A.
mediaType
chosen
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
B.
mediaTypeAvailable
Indicates that a particular type or format of media is available for use, access, or distribution in the given context.
-
C.
mediaTypeExample
Indicates that something serves as an example or illustrative instance of a particular media type.
-
D.
mediaTypeManaged
Indicates that one entity is responsible for controlling, organizing, or overseeing the specified media type associated with another entity.
-
E.
mediaTypeRecognized
Indicates that a system has successfully identified and accepted the type or format of a given media item as valid or supported.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.