Triple
T35545883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazel Lavery |
E1027211
|
entity |
| Predicate | depictionUsedOn |
P34220
|
FINISHED |
| Object | Irish banknotes |
—
|
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: Irish banknotes | Statement: [Hazel Lavery, depictionUsedOn, Irish banknotes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictionUsedOn Context triple: [Hazel Lavery, depictionUsedOn, Irish banknotes]
-
A.
commonlyDepictedOn
chosen
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
-
B.
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.
-
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.
depictionType
Indicates the specific manner or style in which something is visually represented or depicted.
-
E.
depictionPurpose
Indicates that one entity is depicted specifically for the purpose or function it serves in relation to another entity.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:04 p.m.