Triple
T631769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Northern Command |
E15940
|
entity |
| Predicate | coordinatesDefenseSupport |
P17294
|
FINISHED |
| Object | Federal civil authorities |
—
|
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: Federal civil authorities | Statement: [U.S. Northern Command, coordinatesDefenseSupport, Federal civil authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatesDefenseSupport Context triple: [U.S. Northern Command, coordinatesDefenseSupport, Federal civil authorities]
-
A.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
-
B.
defensiveOperation
Indicates actions or measures undertaken to protect, guard, or defend a target against threats or attacks.
-
C.
combatantCommandSupport
Indicates that one combatant provides command-related support or assistance to another combatant or combat unit.
-
D.
allianceSupport
Indicates a cooperative relationship where one party provides assistance, resources, or backing to an ally within the context of an alliance.
-
E.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
- F. None of above. chosen
Provenance (4 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec2a4c08190bc5c6ce8a10b0967 |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.