Triple
T26274916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Naze headland |
E660538
|
entity |
| Predicate | NazeTowerFunction |
P102935
|
FINISHED |
| Object | navigation aid |
—
|
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 aid | Statement: [The Naze headland, NazeTowerFunction, navigation aid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NazeTowerFunction Context triple: [The Naze headland, NazeTowerFunction, navigation aid]
-
A.
towerFunction
Indicates that one entity serves as a tower-like structure or performs the function of a tower in relation to another entity.
-
B.
hasTowerFunction
chosen
Indicates that something serves the role or performs the function of a tower in relation to another entity.
-
C.
timeballTowerFunction
Indicates that something serves the function or role of a time ball tower, typically used to signal standardized time visually.
-
D.
castleFunction
Indicates the primary role, purpose, or use that a castle serves (e.g., defense, residence, administration, or symbolism).
-
E.
isObservationTower
Indicates that something functions as an observation tower, serving primarily as a structure for viewing or monitoring an area from an elevated position.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e33c5748190abaa09d9b0c4c00a |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:54 p.m.