Triple
T4771775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Court Hotel |
E105942
|
entity |
| Predicate | checkOutCategory |
P58695
|
FINISHED |
| Object | morning check-out |
—
|
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: morning check-out | Statement: [Stanford Court Hotel, checkOutCategory, morning check-out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkOutCategory Context triple: [Stanford Court Hotel, checkOutCategory, morning check-out]
-
A.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
-
B.
hasExhibitCategory
Indicates that an exhibit is associated with a particular category or type of exhibit.
-
C.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
D.
categoryStatus
Indicates the current state or condition assigned to a category within a given system or context.
-
E.
announcesCategory
Indicates that an entity publicly declares or makes known a specific category associated with another entity or item.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655e5dcc8190a932be9b1baaffb2 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:21 p.m.