Triple
T14821337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seleucus II Callinicus |
E348458
|
entity |
| Predicate | causeOfWeakening |
P36830
|
FINISHED |
| Object | dynastic conflicts |
—
|
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: dynastic conflicts | Statement: [Seleucus II Callinicus, causeOfWeakening, dynastic conflicts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfWeakening Context triple: [Seleucus II Callinicus, causeOfWeakening, dynastic conflicts]
-
A.
causeOfWeakness
chosen
Indicates that one entity is the reason or source that brings about the weakness of another entity.
-
B.
weakenedDuring
Indicates that an entity’s strength, intensity, or effectiveness is reduced over the course of a specified time period or event.
-
C.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
D.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe64328819083ce42704cf0602d |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:50 a.m.