Triple
T21176548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocracoke Lighthouse |
E521825
|
entity |
| Predicate | interiorAccess |
P143167
|
FINISHED |
| Object | not generally open to 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: not generally open to public | Statement: [Ocracoke Lighthouse, interiorAccess, not generally open to public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorAccess Context triple: [Ocracoke Lighthouse, interiorAccess, not generally open to public]
-
A.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
floorAccess
Indicates that an entity is permitted to enter or use a specific floor or level within a building or structure.
-
C.
hasDomeOrRoofAccess
Indicates that an entity has access to, or the ability to reach or use, a dome or roof area associated with another entity.
-
D.
residenceAccessed
Indicates that an entity has entered, used, or otherwise gained access to a particular residence.
-
E.
hasTypicalAtticAccess
Indicates that an entity has a standard or commonly used means of accessing an attic space.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e730197cfc8190bde13453b761886b |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3 p.m.