Triple
T22836012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman of Bulgaria |
E565948
|
entity |
| Predicate | heldTitleWhileInCaptivity |
P149908
|
FINISHED |
| Object | Tsar of Bulgaria |
—
|
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: Tsar of Bulgaria | Statement: [Roman of Bulgaria, heldTitleWhileInCaptivity, Tsar of Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTitleWhileInCaptivity Context triple: [Roman of Bulgaria, heldTitleWhileInCaptivity, Tsar of Bulgaria]
-
A.
periodOfCaptivity
Indicates a time span during which an entity is held in captivity or confinement.
-
B.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
C.
heldTitleUnder
Indicates that one entity possessed or occupied a particular title, rank, or office under the authority, jurisdiction, or auspices of another entity.
-
D.
heldCaptive
Indicates that one entity is being forcibly confined or restrained by another, preventing their freedom of movement or escape.
-
E.
wasDetainedDuring
Indicates that an entity was held in custody or confinement for some period of time during a specified event or time interval.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2f09608190bc8e465e53b39e2e |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:35 p.m.