Triple
T36002166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | باب الرحمة |
E1041161
|
entity |
| Predicate | closedToOutsideAccess |
P119694
|
FINISHED |
| Object | نعم |
—
|
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: نعم | Statement: [باب الرحمة, closedToOutsideAccess, نعم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToOutsideAccess Context triple: [باب الرحمة, closedToOutsideAccess, نعم]
-
A.
closedToPublic
Indicates that access to the referenced entity is restricted so that the general public is not allowed to enter or use it.
-
B.
closedOffFrom
chosen
Indicates that one entity is isolated, blocked, or prevented from accessing, interacting with, or being influenced by another entity.
-
C.
closedForSafety
Indicates that an entity (such as a place, facility, or route) is temporarily unavailable or inaccessible due to safety concerns or hazards.
-
D.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
E.
closedAgainst
Indicates that an entity has been closed or shut in opposition to, or as a barrier against, another entity.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:07 p.m.