Triple
T19804871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARCENT |
E475782
|
entity |
| Predicate | alliesCooperatedWith |
P136406
|
FINISHED |
| Object | partner land forces in the CENTCOM region |
—
|
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: partner land forces in the CENTCOM region | Statement: [ARCENT, alliesCooperatedWith, partner land forces in the CENTCOM region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliesCooperatedWith Context triple: [ARCENT, alliesCooperatedWith, partner land forces in the CENTCOM region]
-
A.
oftenAlliedWith
Indicates that one entity is frequently or habitually allied or aligned in cooperation with another entity.
-
B.
alliesOf
chosen
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
C.
laterAlliesWith
Indicates that two entities become allies at a later time, after not being allied initially.
-
D.
alliesIncluded
Indicates that the specified set or group explicitly includes one or more allied entities as members.
-
E.
historicallyAlliedWith
Indicates that two entities have been political, military, or strategic allies during some period in the past.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65427546c819082c8eb0d63e3f5fe |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.