Triple
T9633242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanikai Pillbox Trail |
E232856
|
entity |
| Predicate | bunkersPurpose |
P89370
|
FINISHED |
| Object | coastal observation |
—
|
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: coastal observation | Statement: [Lanikai Pillbox Trail, bunkersPurpose, coastal observation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bunkersPurpose Context triple: [Lanikai Pillbox Trail, bunkersPurpose, coastal observation]
-
A.
hasBunkers
Indicates that one entity possesses or contains bunkers, such as fortified shelters or storage structures, as part of its features or infrastructure.
-
B.
hasEstimatedNumberOfBunkers
Indicates that an entity is associated with an approximate or estimated count of bunkers.
-
C.
burrowUse
Indicates that an entity makes use of a burrow, typically as a shelter, nesting site, or refuge.
-
D.
towerPurpose
Indicates the primary function or intended use that a tower is designed or employed to serve.
-
E.
usedFortificationsAt
Indicates that an entity employed or deployed specific fortifications in a particular context, such as a battle, campaign, or defensive situation.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b28ce2c819086d3c6e4e6ea95a7 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:11 p.m.