Triple
T18774585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horkos |
E459102
|
entity |
| Predicate | symbolicType |
P13707
|
FINISHED |
| Object | abstract personification |
—
|
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: abstract personification | Statement: [Horkos, symbolicType, abstract personification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicType Context triple: [Horkos, symbolicType, abstract personification]
-
A.
symbolType
chosen
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
B.
symbolicAspect
Indicates that one entity functions as a symbol or emblem that represents, expresses, or conveys a particular meaning, quality, or concept of another entity.
-
C.
symbolIs
Indicates that one entity serves as the symbolic representation or sign of another entity.
-
D.
syntacticType
Indicates the grammatical or structural category that characterizes how an expression functions within a syntactic construction.
-
E.
symbolicRelation
Indicates a relationship where one entity stands for, represents, or conveys meaning about another through symbols or abstract signs.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933888408190a21f9ac5b360d1eb |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.