Triple
T2703647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaquina Head Lighthouse |
E59292
|
entity |
| Predicate | attachedStructures |
P10139
|
FINISHED |
| Object | keeper’s dwelling (originally) |
—
|
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: keeper’s dwelling (originally) | Statement: [Yaquina Head Lighthouse, attachedStructures, keeper’s dwelling (originally)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attachedStructures Context triple: [Yaquina Head Lighthouse, attachedStructures, keeper’s dwelling (originally)]
-
A.
towerAttachment
Indicates that one entity is physically attached to or structurally connected with a tower.
-
B.
buildingIncorporatedInto
Indicates that one building has been structurally or functionally integrated into another building as part of a combined or expanded construction.
-
C.
annexStructure
Indicates that one structure is attached or added to another as an annex or extension.
-
D.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
E.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda5011bc8190ae4e41da391e759c |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.