Triple
T10398890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Air Station San Diego |
E245090
|
entity |
| Predicate | militaryCategory |
P23907
|
FINISHED |
| Object | naval air facility |
—
|
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: naval air facility | Statement: [Naval Air Station San Diego, militaryCategory, naval air facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCategory Context triple: [Naval Air Station San Diego, militaryCategory, naval air facility]
-
A.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
B.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
C.
armamentCategory
Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
-
D.
militaryUse
chosen
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
E.
militaryTechnology
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9d1f2408190beaa8197641c66b4 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:07 p.m.