Triple
T36491383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flickr8k |
E899058
|
entity |
| Predicate | hasCaptionSource |
P201044
|
FINISHED |
| Object | human annotators |
—
|
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: human annotators | Statement: [Flickr8k, hasCaptionSource, human annotators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaptionSource Context triple: [Flickr8k, hasCaptionSource, human annotators]
-
A.
hasCaptionsPerImage
Indicates that each image is associated with one or more textual captions.
-
B.
hasNotabilitySource
Indicates that there exists an external, recognized source that attests to or supports the notability or significance of the subject entity.
-
C.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
D.
hasTitleInSources
Indicates that an entity is associated with a specific title as it appears in one or more referenced sources.
-
E.
hasMainImageSource
Indicates that an entity is associated with a primary image file or URL that serves as its main visual representation.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
| PDg | Predicate description generation | batch_69ffc3eed97c819085c06ffe3699ff38 |
completed | May 9, 2026, 11:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.