Triple
T15003928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eirene |
E377659
|
entity |
| Predicate | isTheophoricOrConceptName |
P9869
|
FINISHED |
| Object | abstract concept of peace |
—
|
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 concept of peace | Statement: [Eirene, isTheophoricOrConceptName, abstract concept of peace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTheophoricOrConceptName Context triple: [Eirene, isTheophoricOrConceptName, abstract concept of peace]
-
A.
isTheophoric
chosen
Indicates that something (typically a name or term) incorporates the name of a deity or refers explicitly to a god.
-
B.
isPraenomenOf
Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
-
C.
isEarlyNameOf
Indicates that one name is an earlier or former designation for the same entity as another name.
-
D.
isOccupationalOrToponymic
Indicates that a name or term is derived either from an occupation (job or role) or from a place (toponymic origin).
-
E.
hasPantheonName
Indicates that an entity is associated with a specific pantheon and is identified by the given pantheon name.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7312ae48190bdaf91ecced6657e |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.