Triple
T19153809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Map of Love |
E468873
|
entity |
| Predicate | hasSurrealImagery |
P77463
|
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: [The Map of Love, hasSurrealImagery, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurrealImagery Context triple: [The Map of Love, hasSurrealImagery, true]
-
A.
hasSurrealElements
chosen
Indicates that something contains dreamlike, bizarre, or illogical features that depart from ordinary reality.
-
B.
hasAllegoricalDepictionsBy
Indicates that one entity is represented through allegorical depictions created by another entity.
-
C.
containsSupernaturalElement
Indicates that the subject involves or features a supernatural, magical, or otherworldly element beyond normal natural laws.
-
D.
containsVisionOf
Indicates that one entity includes, depicts, or embodies a visual representation or image of another entity.
-
E.
hasAllegoricalFigures
Indicates that a work, scene, or element includes figures that symbolically represent abstract ideas, concepts, or moral qualities.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb81bf08190b0352137eb4a5763 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.