Triple
T15784972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discovery Cove |
E382713
|
entity |
| Predicate | includesWithAdmission |
P119998
|
FINISHED |
| Object | food and beverages |
—
|
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: food and beverages | Statement: [Discovery Cove, includesWithAdmission, food and beverages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesWithAdmission Context triple: [Discovery Cove, includesWithAdmission, food and beverages]
-
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.
admissionRequired
Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
-
D.
admittedTo
Indicates that one entity has been formally accepted, enrolled, or granted entry into another entity, such as an institution, program, or facility.
-
E.
usedToAdmit
Indicates that something served as the means or instrument by which an entity was allowed or granted entry or access.
- F. None of above. chosen
Provenance (4 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05401c4788190a31c180953433db9 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e006b17f7881908b8c7a37f0af4581 |
completed | April 15, 2026, 9:44 p.m. |
Created at: April 10, 2026, 4:48 a.m.