Triple
T16785101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhodian–Quill conflict |
E407950
|
entity |
| Predicate | isDepictedVia |
P124622
|
FINISHED |
| Object | flashbacks in Class |
—
|
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: flashbacks in Class | Statement: [Rhodian–Quill conflict, isDepictedVia, flashbacks in Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDepictedVia Context triple: [Rhodian–Quill conflict, isDepictedVia, flashbacks in Class]
-
A.
imageDepictedIn
Indicates that a particular image is shown, represented, or included within another resource or context.
-
B.
depicts
Indicates that one entity visually represents, portrays, or shows another entity.
-
C.
commonlyDepictedOn
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
-
D.
intendedToDepict
Indicates that one entity was purposefully created or selected in order to visually represent or portray another entity.
-
E.
depictionType
Indicates the specific manner or style in which something is visually represented or depicted.
- F. None of above. chosen
Provenance (4 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21996cc81909deb88545af7079f |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.