Triple
T36234632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longstone |
E891343
|
entity |
| Predicate | lighthouseBuiltFor |
P184791
|
FINISHED |
| Object | navigation safety in Farne Islands |
—
|
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: navigation safety in Farne Islands | Statement: [Longstone, lighthouseBuiltFor, navigation safety in Farne Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lighthouseBuiltFor Context triple: [Longstone, lighthouseBuiltFor, navigation safety in Farne Islands]
-
A.
lighthouseConstructedIn
Indicates that a lighthouse was built or established during a specific time period or in a specific year.
-
B.
lighthouseType
Indicates the specific classification or category of a lighthouse based on its design, function, or operational characteristics.
-
C.
lighthouseLocatedAt
Indicates that a lighthouse is situated at or associated with a specific geographic location.
-
D.
lighthouseHeight
Indicates the vertical measurement of a lighthouse from its base to its top.
-
E.
lighthouseBuilder
Indicates that one entity is the builder or constructor responsible for creating a lighthouse associated with another entity.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5f89c5c8190825ed5d4317c540c |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.