Triple
T34006813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KBLV |
E871987
|
entity |
| Predicate | militaryUnitPresent |
P14275
|
FINISHED |
| Object | Scott Air Force Base units |
—
|
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: Scott Air Force Base units | Statement: [KBLV, militaryUnitPresent, Scott Air Force Base units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryUnitPresent Context triple: [KBLV, militaryUnitPresent, Scott Air Force Base units]
-
A.
hasMilitaryPresence
chosen
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
B.
isAboutMilitaryUnit
Indicates that something (such as a document, statement, or resource) concerns, discusses, or pertains to a specific military unit.
-
C.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
D.
portraysMilitaryUnit
Indicates that one entity visually or narratively represents, depicts, or shows a specific military unit.
-
E.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:50 a.m.