Triple
T34507145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boerebista |
E885918
|
entity |
| Predicate | realmFragmentedAfterDeath |
P179425
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Boerebista, realmFragmentedAfterDeath, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmFragmentedAfterDeath Context triple: [Boerebista, realmFragmentedAfterDeath, true]
-
A.
deathRealm
Indicates a realm, domain, or state specifically associated with death or the dead.
-
B.
realmFallenTo
Indicates that control or possession of a realm has been lost by one party and come under the domination of another, typically through defeat or collapse.
-
C.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
D.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
-
E.
releasedAfterDeathOf
Indicates that something (such as a work, product, or announcement) was released only after the death of a specified person.
- F. None of above. chosen
Provenance (4 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 2:01 a.m.