Triple
T16517595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soto Cano Air Base |
E401223
|
entity |
| Predicate | hasTypeOfPresence |
P31835
|
FINISHED |
| Object | non-permanent U.S. troop presence |
—
|
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: non-permanent U.S. troop presence | Statement: [Soto Cano Air Base, hasTypeOfPresence, non-permanent U.S. troop presence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPresence Context triple: [Soto Cano Air Base, hasTypeOfPresence, non-permanent U.S. troop presence]
-
A.
typeOfPresence
chosen
Indicates the manner or mode in which an entity is present or exists in relation to another entity, context, or environment.
-
B.
hasPresenterType
Indicates the specific role or category of presenter associated with an event, item, or presentation.
-
C.
hasParType
Indicates that an entity has a specific parent type or category to which it belongs.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7da2248190a540a5ef8686963d |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.