Triple
T18774188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponos |
E459091
|
entity |
| Predicate | widerCategory |
P58049
|
FINISHED |
| Object | personifications in Greek mythology |
—
|
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: personifications in Greek mythology | Statement: [Ponos, widerCategory, personifications in Greek mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widerCategory Context triple: [Ponos, widerCategory, personifications in Greek mythology]
-
A.
cornerCategory
Indicates that something is classified as belonging to a specific type or category of corner.
-
B.
widerUsage
Indicates that one entity is used or applied more broadly, frequently, or in a greater variety of contexts than another.
-
C.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
D.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
E.
generalCategory
chosen
Indicates that one entity is classified as a broad or overarching category to which the other entity belongs.
- 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.