Triple
T27035714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zona A |
E681045
|
entity |
| Predicate | militaryPresenceOf |
P14275
|
FINISHED |
| Object | United States Army |
—
|
NE NERFINISHED |
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: United States Army | Statement: [Zona A, militaryPresenceOf, United States Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryPresenceOf Context triple: [Zona A, militaryPresenceOf, United States Army]
-
A.
hasMilitaryPresence
chosen
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
B.
militaryBasis
Indicates that one entity serves as the foundational military justification, rationale, or underlying military reason for another entity or action.
-
C.
civilianPresence
Indicates the presence or involvement of non-combatant individuals in a given location, situation, or event.
-
D.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
E.
hasArmedForces
Indicates that an entity possesses or maintains organized military forces under its control.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 7:16 a.m.