Triple
T4661596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormalong Bay pool complex |
E102544
|
entity |
| Predicate | hasEntryPolicy |
P48724
|
FINISHED |
| Object | room key access for resort guests |
—
|
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: room key access for resort guests | Statement: [Stormalong Bay pool complex, hasEntryPolicy, room key access for resort guests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntryPolicy Context triple: [Stormalong Bay pool complex, hasEntryPolicy, room key access for resort guests]
-
A.
hasKeyPolicy
chosen
Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
-
B.
hasReferencePolicy
Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
-
C.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
D.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
E.
containsPolicyOn
Indicates that one entity includes, references, or incorporates a specific policy within it.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd632b7fb88190821f213620719d6b |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.