Triple
T31306882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chihriq fortress |
E798355
|
entity |
| Predicate | purposeOfBábImprisonment |
P22043
|
FINISHED |
| Object | isolation of the Báb from followers |
—
|
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: isolation of the Báb from followers | Statement: [Chihriq fortress, purposeOfBábImprisonment, isolation of the Báb from followers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfBábImprisonment Context triple: [Chihriq fortress, purposeOfBábImprisonment, isolation of the Báb from followers]
-
A.
conditionDuringBábImprisonment
Indicates that the specified condition or state holds during the period of the Báb’s imprisonment.
-
B.
hadLeaderAfterTheBáb
Indicates that an entity had a recognized leader who assumed leadership after the Báb.
-
C.
periodOfCaptivity
Indicates a time span during which an entity is held in captivity or confinement.
-
D.
usedForImprisoning
chosen
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
-
E.
سبب_عذاب_قومه
Indicates that something is the cause or reason for the punishment inflicted upon a particular people.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:14 p.m.