Triple
T36021638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DBR-1 |
E1042003
|
entity |
| Predicate | usedForIntelligenceOn |
P32507
|
FINISHED |
| Object | NATO adversaries |
—
|
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: NATO adversaries | Statement: [DBR-1, usedForIntelligenceOn, NATO adversaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForIntelligenceOn Context triple: [DBR-1, usedForIntelligenceOn, NATO adversaries]
-
A.
usesIntelligence
Indicates that an entity applies mental abilities such as reasoning, problem-solving, or understanding to perform an action or achieve a goal.
-
B.
isBelievedToBeUsedFor
Indicates that something is thought or assumed to serve a particular purpose or function, without certainty.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
providesIntelligenceTo
chosen
Indicates that one entity supplies information, analysis, or insight that enhances the knowledge or decision-making capability of another entity.
-
E.
intelligenceUse
Indicates the use or application of intelligence by one entity toward a task, situation, or another entity.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:07 p.m.