Triple
T9404616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Dodon |
E226553
|
entity |
| Predicate | breaksPromiseTo |
P40216
|
FINISHED |
| Object | astrologer |
—
|
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: astrologer | Statement: [Tsar Dodon, breaksPromiseTo, astrologer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksPromiseTo Context triple: [Tsar Dodon, breaksPromiseTo, astrologer]
-
A.
breaksWith
chosen
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
B.
promises
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
C.
isBrokenBy
Indicates that one entity causes another entity to become damaged, nonfunctional, or destroyed.
-
D.
canBreakOutTo
Indicates that one entity has the ability or permission to escape or exit from the context, boundary, or containment defined by another entity.
-
E.
breaksOn
Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c125dc8190a6438cf0ee23e7a9 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.