Triple
T15442035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Red Gold |
E369927
|
entity |
| Predicate | metaphoricalReference |
P93472
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [City of Red Gold, metaphoricalReference, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metaphoricalReference Context triple: [City of Red Gold, metaphoricalReference, gold]
-
A.
hasMetaphoricalForm
Indicates that one entity is expressed, represented, or understood through a metaphorical form or figurative expression involving another entity.
-
B.
figurativeMeaning
chosen
Indicates that one entity is used in a non-literal, metaphorical, or symbolic sense to convey a meaning about another entity or concept.
-
C.
hasMetaphoricalContent
Indicates that something contains or expresses meaning through metaphorical, rather than purely literal, content.
-
D.
keyMetaphor
Indicates that one entity functions as a central or primary metaphor used to conceptualize, explain, or structure understanding of another entity.
-
E.
titleMetaphor
Indicates that the title of a work functions metaphorically, expressing a figurative or symbolic meaning rather than a literal one.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef55f5c8190a32b1b6ad1daf454 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.