Triple
T23565061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Broken Trident |
E579346
|
entity |
| Predicate | tridentOriginSymbolism |
P69757
|
FINISHED |
| Object | Neptune’s trident |
—
|
NE NERFINISHED |
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: Neptune’s trident | Statement: [The Broken Trident, tridentOriginSymbolism, Neptune’s trident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tridentOriginSymbolism Context triple: [The Broken Trident, tridentOriginSymbolism, Neptune’s trident]
-
A.
tridentProngsSymbolize
Indicates that the prongs of a trident serve as symbols representing particular concepts, powers, or attributes in relation to something.
-
B.
tridentBrokenShaftSymbolizes
chosen
Indicates that a broken trident shaft serves as a symbol representing a particular concept, state, or message.
-
C.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
D.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
E.
treeSymbolism
Indicates the use of a tree as a symbolic representation of an idea, quality, or relationship between entities.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6b04cc81909385e485b8bdd54b |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:34 p.m.