Triple
T1999011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitney Portal Campground |
E43420
|
entity |
| Predicate | hasCheckInSystem |
P35391
|
FINISHED |
| Object | campground host (seasonal) |
—
|
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: campground host (seasonal) | Statement: [Whitney Portal Campground, hasCheckInSystem, campground host (seasonal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInSystem Context triple: [Whitney Portal Campground, hasCheckInSystem, campground host (seasonal)]
-
A.
hasCheckInBuilding
Indicates that an entity has performed a check-in event within a specified building.
-
B.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
-
C.
hasCheckInCounters
Indicates that an entity is associated with one or more check-in counters used for processing arrivals or registrations.
-
D.
hasCheckOutTime
Indicates the specific time at which an entity is required or scheduled to check out or depart.
-
E.
requiresCheckIn
Indicates that one entity must perform a check-in action or be checked in as a prerequisite for another entity, event, or process to proceed.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb90ec7948190bbfb0329e9e67cca |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:37 p.m.