Triple
T20095101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neist Point Lighthouse |
E496377
|
entity |
| Predicate | keeperAccommodationStatus |
P138688
|
FINISHED |
| Object | privately owned |
—
|
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: privately owned | Statement: [Neist Point Lighthouse, keeperAccommodationStatus, privately owned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keeperAccommodationStatus Context triple: [Neist Point Lighthouse, keeperAccommodationStatus, privately owned]
-
A.
reservationStatus
Indicates the current state or condition of a reservation within its lifecycle (e.g., pending, confirmed, canceled, completed).
-
B.
villaCurrentStatus
Indicates the current operational or condition status assigned to a villa at a given point in time.
-
C.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
D.
hasReservationStatus
Indicates that an entity is associated with a specific reservation and the current status or state of that reservation (e.g., pending, confirmed, canceled).
-
E.
sitterStatus
Indicates the current role, availability, or engagement state of a sitter in relation to a sitting arrangement or service.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666b891c8190b4e4a60b73728771 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:24 p.m.