Triple
T11717231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Moore Lighthouse |
E278529
|
entity |
| Predicate | towerAccess |
P74961
|
FINISHED |
| Object | generally closed to the public |
—
|
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: generally closed to the public | Statement: [Point Moore Lighthouse, towerAccess, generally closed to the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerAccess Context triple: [Point Moore Lighthouse, towerAccess, generally closed to the public]
-
A.
towerAccessibleTo
chosen
Indicates that a particular tower can be reached, entered, or used by a specified agent or group under given conditions.
-
B.
towerAccessibleBy
Indicates that a tower can be reached or entered via a specified route, path, or means of access.
-
C.
towerAttachment
Indicates that one entity is physically attached to or structurally connected with a tower.
-
D.
towerFunction
Indicates that one entity serves as a tower-like structure or performs the function of a tower in relation to another entity.
-
E.
tourAccess
Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c10d988190842acd824135cf15 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.