Triple
T13452150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bab al-Rahma |
E320632
|
entity |
| Predicate | sealedSince |
P69347
|
FINISHED |
| Object | early Islamic period |
—
|
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: early Islamic period | Statement: [Bab al-Rahma, sealedSince, early Islamic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sealedSince Context triple: [Bab al-Rahma, sealedSince, early Islamic period]
-
A.
sealedBy
Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of another entity.
-
B.
controlledSince
Indicates that one entity has held control or authority over another entity starting from a specified point in time.
-
C.
protectedSince
Indicates that one entity has been under protection by another entity starting from a specified point in time and continuing thereafter.
-
D.
isSealed
chosen
Indicates that an entity is closed off or secured so that nothing can enter, exit, or be altered.
-
E.
coveredSince
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaefae85481909e6a59797cbb25e7 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.