Triple
T28845954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Ténèbres |
E728453
|
entity |
| Predicate | mainImageryType |
P77285
|
FINISHED |
| Object | dream 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: dream imagery | Statement: [Les Ténèbres, mainImageryType, dream imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainImageryType Context triple: [Les Ténèbres, mainImageryType, dream imagery]
-
A.
mapsType
Indicates that one entity serves as a mapping whose values or outputs are of the specified type.
-
B.
cartographicType
Indicates the specific kind or category of cartographic representation associated with an entity (e.g., map type or mapping style).
-
C.
hasImageryFrom
Indicates that one entity contains, incorporates, or is derived from the imagery produced or provided by another entity.
-
D.
hasColorImagery
Indicates that something includes or is characterized by visual elements emphasizing specific colors or color-based symbolism.
-
E.
hasImageryType
chosen
Indicates that one entity is associated with a specific kind or category of imagery (such as visual style, medium, or representation type) used to depict or describe it.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659d446708190aaa57d5a1181209e |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:42 a.m.