Triple
T38042009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cockspur Island |
E949508
|
entity |
| Predicate | hasNearbyNavigationAid |
P37483
|
FINISHED |
| Object | Cockspur Island Lighthouse |
—
|
NE NERFINISHED |
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: Cockspur Island Lighthouse | Statement: [Cockspur Island, hasNearbyNavigationAid, Cockspur Island Lighthouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyNavigationAid Context triple: [Cockspur Island, hasNearbyNavigationAid, Cockspur Island Lighthouse]
-
A.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
B.
isNavigationalAid
chosen
Indicates that one entity serves as a navigational aid or guide to help locate, orient, or move toward another entity or destination.
-
C.
navigationAidIdentifier
Indicates that an entity is assigned or associated with an identifier used to uniquely reference a specific navigation aid.
-
D.
hasNavigationAidSupport
Indicates that an entity provides or is compatible with tools or systems that assist with navigation.
-
E.
positionOnAid
Indicates a stance or viewpoint that an entity holds regarding the provision, use, or policy of aid.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:20 p.m.