Triple
T33354567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bartsch 1 |
E854033
|
entity |
| Predicate | refersToDepictedSubjects |
P49267
|
FINISHED |
| Object | biblical Adam |
—
|
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: biblical Adam | Statement: [Bartsch 1, refersToDepictedSubjects, biblical Adam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToDepictedSubjects Context triple: [Bartsch 1, refersToDepictedSubjects, biblical Adam]
-
A.
depictedSubject
chosen
Indicates that one entity visually represents or portrays another entity as its subject in an image or depiction.
-
B.
commonlyDepictedOn
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
-
C.
depictionIncludes
Indicates that a depiction (such as an image, illustration, or visual representation) contains or shows the referenced entity as part of its visual content.
-
D.
typicallyDepicts
Indicates that one entity is most commonly or characteristically portrayed or represented by the other in depictions or images.
-
E.
imageDepictedIn
Indicates that a particular image is shown, represented, or included within another resource or context.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 1, 2026, 1:34 a.m.