Triple
T18885864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchcape Rock Lighthouse |
E461953
|
entity |
| Predicate | hasKeeperStatus |
P118169
|
FINISHED |
| Object | now unmanned |
—
|
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: now unmanned | Statement: [Inchcape Rock Lighthouse, hasKeeperStatus, now unmanned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeeperStatus Context triple: [Inchcape Rock Lighthouse, hasKeeperStatus, now unmanned]
-
A.
hasLockKeeper
Indicates that an entity is associated with or managed by a specific lock keeper (e.g., the person responsible for operating or overseeing a lock).
-
B.
hasKeeperHouse
Indicates that an entity is associated with or assigned to a specific keeper’s house or residence.
-
C.
currentKeepStatus
Indicates the present retention or preservation state currently assigned to an entity.
-
D.
hasOccupantStatus
chosen
Indicates that an entity holds a particular role, status, or condition as an occupant of another entity (such as a place, vehicle, or property).
-
E.
hasKeeperQuartersUse
Indicates that something is used as living or working quarters for a keeper or caretaker.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c4760d808190b502c4ed1f24424c |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.