Triple
T31324243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axieros |
E798836
|
entity |
| Predicate | equatedByAncientsWith |
P157970
|
FINISHED |
| Object | Demeter |
—
|
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: Demeter | Statement: [Axieros, equatedByAncientsWith, Demeter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equatedByAncientsWith Context triple: [Axieros, equatedByAncientsWith, Demeter]
-
A.
associatedWithAncientEmpire
Indicates that one entity has a historical, cultural, political, or geographic connection or affiliation with an ancient empire.
-
B.
knownToAncientGreeks
Indicates that something was recognized, identified, or understood by people in ancient Greek societies.
-
C.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
D.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
E.
ancientAttributionBy
chosen
Indicates that an entity is credited or assigned to another entity based on ancient or historical sources rather than modern evidence.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69eb008808190bdf42de72d202baf |
completed | May 3, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.