Triple
T13704350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Island |
E328600
|
entity |
| Predicate | hasMilitaryRelevance |
P27512
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lincoln Island, hasMilitaryRelevance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryRelevance Context triple: [Lincoln Island, hasMilitaryRelevance, yes]
-
A.
hasMilitarySignificance
chosen
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
-
B.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
C.
hasMilitarySecurity
Indicates that an entity provides, maintains, or is responsible for military protection or defense for another entity or area.
-
D.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
E.
militaryImportance
Indicates the degree to which something is strategically or operationally significant to military objectives or capabilities.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.