Triple
T37197979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleventh Labour of Heracles |
E921644
|
entity |
| Predicate | appleSymbolism |
P129
|
FINISHED |
| Object | immortality |
—
|
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: immortality | Statement: [Eleventh Labour of Heracles, appleSymbolism, immortality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appleSymbolism Context triple: [Eleventh Labour of Heracles, appleSymbolism, immortality]
-
A.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
B.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
C.
eyeSymbolism
Indicates the use of eyes or eye-related imagery to symbolically represent deeper meanings, concepts, or themes in a context.
-
D.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
macMeaning
Indicates that one entity specifies or conveys the meaning or semantic interpretation of another entity within a mac-related context (e.g., a term, code, or identifier).
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:15 p.m.