Triple
T30355150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Rawdah ash-Sharifah |
E772121
|
entity |
| Predicate | hasVisitationRule |
P10265
|
FINISHED |
| Object | separate visitation times for men and women |
—
|
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: separate visitation times for men and women | Statement: [Al-Rawdah ash-Sharifah, hasVisitationRule, separate visitation times for men and women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitationRule Context triple: [Al-Rawdah ash-Sharifah, hasVisitationRule, separate visitation times for men and women]
-
A.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
B.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
hasVisitationPurpose
Indicates that an entity’s visit to another entity or location is associated with a specific purpose or reason.
-
D.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
E.
hasVisitorPolicy
chosen
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 7:56 p.m.