Triple
T14465395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Bateau ivre |
E358692
|
entity |
| Predicate | imageryDomain |
P17123
|
FINISHED |
| Object | maritime imagery |
—
|
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: maritime imagery | Statement: [Le Bateau ivre, imageryDomain, maritime imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imageryDomain Context triple: [Le Bateau ivre, imageryDomain, maritime imagery]
-
A.
usesImagery
Indicates that one entity employs descriptive or figurative language to create sensory or vivid mental images in relation to another entity or concept.
-
B.
usesImageryOf
chosen
Indicates that one entity employs or incorporates visual or sensory imagery that depicts, references, or symbolically represents another entity.
-
C.
evokesImageOf
Indicates that one entity triggers or brings to mind a mental image or visual representation of another entity.
-
D.
imageOf
Indicates that one entity is a visual representation or depiction of another entity.
-
E.
imagedBy
Indicates that something is captured, recorded, or represented in an image created by a particular imaging device, method, or agent.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f6d4c08190a12e9a5901ee3508 |
completed | April 14, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.