Triple
T19686213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupus |
E472717
|
entity |
| Predicate | hasTraditionalDepiction |
P5310
|
FINISHED |
| Object | wolf |
—
|
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: wolf | Statement: [Lupus, hasTraditionalDepiction, wolf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalDepiction Context triple: [Lupus, hasTraditionalDepiction, wolf]
-
A.
hasIconographicTradition
chosen
Indicates that an entity is associated with a recognized, recurring set of visual motifs or symbolic representations within a particular artistic or cultural tradition.
-
B.
hasAllegoricalDepictionsBy
Indicates that one entity is represented through allegorical depictions created by another entity.
-
C.
hasCulturalDepiction
Indicates that one entity is represented, portrayed, or depicted in the cultural work or expression of another entity.
-
D.
isDepictedVia
Indicates that one entity is represented, illustrated, or shown by means of another entity, such as a specific medium, style, or method of depiction.
-
E.
hasIconographicFigure
Indicates that one entity includes, depicts, or is associated with a particular iconographic figure in its visual or symbolic representation.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420c3f50819082b64b1fa4335e56 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.