Triple
T37305688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun of Justice |
E926072
|
entity |
| Predicate | hasMetaphoricalDomain |
P155063
|
FINISHED |
| Object | sun |
—
|
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: sun | Statement: [Sun of Justice, hasMetaphoricalDomain, sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetaphoricalDomain Context triple: [Sun of Justice, hasMetaphoricalDomain, sun]
-
A.
hasMetaphoricalForm
Indicates that one entity is expressed, represented, or understood through a metaphorical form or figurative expression involving another entity.
-
B.
hasMetaphoricalSubject
chosen
Indicates that one entity functions as the metaphorical subject or source domain in a figurative or metaphorical expression involving another entity.
-
C.
hasMetaphoricalContent
Indicates that something contains or expresses meaning through metaphorical, rather than purely literal, content.
-
D.
hasMetaphoricalFramework
Indicates that one entity employs or is structured around a metaphorical framework derived from or associated with another entity.
-
E.
hasMetaphorType
Indicates that one entity is classified as having or using a particular type of metaphor in relation to another entity.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: May 3, 2026, 4:16 p.m.