Triple
T35760586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KITLV |
E1033557
|
entity |
| Predicate | hasImageCollection |
P426
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [KITLV, hasImageCollection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImageCollection Context triple: [KITLV, hasImageCollection, true]
-
A.
hasPhotoCollectionContext
Indicates that there exists a contextual relationship between an entity and a collection of photos, specifying the circumstances or scope in which that photo collection is relevant or used.
-
B.
hasPhotographicCollectionAt
Indicates that an entity maintains or possesses a photographic collection located at a specified place or institution.
-
C.
hasImageFeature
Indicates that an entity is associated with a specific visual characteristic or attribute extracted from an image.
-
D.
hasCollection
chosen
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
E.
containsImage
Indicates that one entity includes or embeds an image as part of its content or structure.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.