Triple
T26019008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Osprey at Beaver Creek |
E647104
|
entity |
| Predicate | checkInActivity |
P12450
|
FINISHED |
| Object | hotel check-in |
—
|
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: hotel check-in | Statement: [The Osprey at Beaver Creek, checkInActivity, hotel check-in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkInActivity Context triple: [The Osprey at Beaver Creek, checkInActivity, hotel check-in]
-
A.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
checkInTime
chosen
Indicates the time at which an entity arrives at and formally registers its presence at a specified place or event.
-
C.
has activity
Indicates that one entity performs, exhibits, or is engaged in a particular action, behavior, or process associated with another entity.
-
D.
hasOnsiteActivity
Indicates that an entity conducts or participates in activities that physically take place at a specific site or location.
-
E.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605bbb17c819080f6b026c2cbc186 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:03 a.m.