Triple
T16203057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QV66 |
E393251
|
entity |
| Predicate | visitorAccessPolicy |
P82756
|
FINISHED |
| Object | limited number of visitors per day |
—
|
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: limited number of visitors per day | Statement: [QV66, visitorAccessPolicy, limited number of visitors per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorAccessPolicy Context triple: [QV66, visitorAccessPolicy, limited number of visitors per day]
-
A.
visitorAccessPoint
Indicates a location or interface through which visitors are allowed to enter, connect, or gain access to a place, system, or resource.
-
B.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
-
C.
visitorAccessibility
Indicates how easily or suitably a place, service, or resource can be used or reached by visitors, including those with varying needs or abilities.
-
D.
visitorManagement
chosen
Indicates the management, tracking, and control of visitors’ access, activities, and permissions within a location or system.
-
E.
visitorRequirement
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2270ca18c8190a259992aed4ec072 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.