Triple
T12673273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shah Cheragh Shrine |
E302739
|
entity |
| Predicate | hasEntranceRequirement |
P36473
|
FINISHED |
| Object | modest dress code |
—
|
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: modest dress code | Statement: [Shah Cheragh Shrine, hasEntranceRequirement, modest dress code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntranceRequirement Context triple: [Shah Cheragh Shrine, hasEntranceRequirement, modest dress code]
-
A.
admissionRequired
Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
-
B.
hasEntryRequirement
chosen
Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
-
C.
boardingRequirement
Indicates the conditions or criteria that must be met for an entity to be allowed to board another entity (such as a vehicle, vessel, or aircraft).
-
D.
hasEntranceRole
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
-
E.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961af991c8190b6079cb57e593b8f |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.