Triple
T8496399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nidhivan |
E201109
|
entity |
| Predicate | accessRule |
P75387
|
FINISHED |
| Object | generally closed to visitors at night |
—
|
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: generally closed to visitors at night | Statement: [Nidhivan, accessRule, generally closed to visitors at night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessRule Context triple: [Nidhivan, accessRule, generally closed to visitors at night]
-
A.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
B.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
C.
accessDeterminedBy
chosen
Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
-
D.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
E.
accessFeature
Indicates that one entity is permitted to use or interact with a specific feature or capability of 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57dbe488190af5f06faf862cd5d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.