Triple
T30094204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Enclosure |
E764817
|
entity |
| Predicate | hasAdmissionControl |
P58
|
FINISHED |
| Object | strict security |
—
|
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: strict security | Statement: [Royal Enclosure, hasAdmissionControl, strict security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdmissionControl Context triple: [Royal Enclosure, hasAdmissionControl, strict security]
-
A.
hasAdmission
Indicates that an entity possesses or is associated with a specific admission event, record, or status (such as being admitted to a place, program, or institution).
-
B.
controlsAdmissionsFor
Indicates that one entity has authority or responsibility over managing and deciding admissions for another entity.
-
C.
includesWithAdmission
Indicates that one entity contains or provides access to another entity, with the latter being available as part of the admission or entry fee.
-
D.
admissionPolicy
chosen
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
E.
admissionQuota
Indicates a specified limit or allocation on the number of admissions allowed for a particular category, program, or period.
- 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_69f22474e4288190b5f895fe3974aa92 |
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:06 p.m.