Triple
T14326931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epiphania |
E355238
|
entity |
| Predicate | wasRenamedDuring |
P39961
|
FINISHED |
| Object | Hellenistic era |
—
|
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: Hellenistic era | Statement: [Epiphania, wasRenamedDuring, Hellenistic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRenamedDuring Context triple: [Epiphania, wasRenamedDuring, Hellenistic era]
-
A.
wasRenamedBackTo
Indicates that an entity, after having its name changed, was later restored to its previous or original name.
-
B.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
C.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
D.
changedNameIn
chosen
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
E.
renamedAfterEvent
Indicates that an entity has changed its name as a consequence of, or in commemoration of, a specific event.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c1c3e70819084b6728ac5c18561 |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.