Triple
T31306845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maku fortress |
E798354
|
entity |
| Predicate | imprisonedPerson |
P41072
|
FINISHED |
| Object | the Báb |
—
|
NE NERFINISHED |
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: the Báb | Statement: [Maku fortress, imprisonedPerson, the Báb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imprisonedPerson Context triple: [Maku fortress, imprisonedPerson, the Báb]
-
A.
imprisonedWith
Indicates that two entities are confined or held in prison together at the same time and place.
-
B.
inmates
chosen
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with another entity.
-
C.
prisonerOf
Indicates that one entity is held in custody or confinement by another entity, typically under legal or authoritative control.
-
D.
convictedIndividual
Indicates that an individual has been found guilty of a crime or offense through a formal legal process and has received a conviction.
-
E.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
- 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_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.