Triple
T22999627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Donkey Colt |
E572599
|
entity |
| Predicate | hasAssociatedImage |
P136026
|
FINISHED |
| Object | young donkey |
—
|
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: young donkey | Statement: [Southern Donkey Colt, hasAssociatedImage, young donkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedImage Context triple: [Southern Donkey Colt, hasAssociatedImage, young donkey]
-
A.
containsImage
Indicates that one entity includes or embeds an image as part of its content or structure.
-
B.
hasImageRole
Indicates that an image is associated with an entity in a specific functional or contextual role (e.g., thumbnail, icon, illustration).
-
C.
hasMainImageSource
Indicates that an entity is associated with a primary image file or URL that serves as its main visual representation.
-
D.
hasImageFeature
Indicates that an entity is associated with a specific visual characteristic or attribute extracted from an image.
-
E.
associatedWithMediaImage
chosen
Indicates a relationship where an entity is linked or connected to a specific media image, such as a photo, illustration, or graphic file.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f6484c8190bfe3f7ea894c43d8 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.