Triple
T31335921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haram area of Mecca |
E799171
|
entity |
| Predicate | entryRestrictedTo |
P8521
|
FINISHED |
| Object | Muslims |
—
|
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: Muslims | Statement: [Haram area of Mecca, entryRestrictedTo, Muslims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryRestrictedTo Context triple: [Haram area of Mecca, entryRestrictedTo, Muslims]
-
A.
accessRestrictedTo
chosen
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
B.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
C.
accessRestrictedSince
Indicates that access to an entity has been limited or blocked starting from a specified point in time.
-
D.
entryControl
Indicates a relationship where one entity regulates or authorizes another entity’s access to a place, system, or resource.
-
E.
eligibilityRestrictedBy
Indicates that an entity’s eligibility for something is limited, constrained, or conditioned by another specified factor or rule.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69ee4d75c819086dbded024eb09c8 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:16 p.m.