Triple
T36491384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flickr8k |
E899058
|
entity |
| Predicate | hasDescriptionQuality |
P200112
|
FINISHED |
| Object | human-written captions |
—
|
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-written captions | Statement: [Flickr8k, hasDescriptionQuality, human-written captions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDescriptionQuality Context triple: [Flickr8k, hasDescriptionQuality, human-written captions]
-
A.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
B.
isDescriptive
Indicates that one entity provides a description or characterization of another entity.
-
C.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
D.
describedThrough
Indicates that something is explained, represented, or conveyed by means of a particular medium, method, or description.
-
E.
hasSurfaceQuality
Indicates that one entity possesses a particular characteristic or condition of its surface.
- 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_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_69ff7594c6c081909e812e4e04e63530 |
completed | May 9, 2026, 5:57 p.m. |
Created at: May 3, 2026, 4:10 p.m.