Triple
T33395539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU solidarity clause |
E855160
|
entity |
| Predicate | assistanceMayInclude |
P176852
|
FINISHED |
| Object | military resources |
—
|
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: military resources | Statement: [EU solidarity clause, assistanceMayInclude, military resources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assistanceMayInclude Context triple: [EU solidarity clause, assistanceMayInclude, military resources]
-
A.
assistance
Indicates providing help, support, or aid from one entity to another to facilitate a task, goal, or need.
-
B.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
-
C.
laterHelps
Indicates that one entity provides help or assistance to another at a subsequent time rather than immediately.
-
D.
soughtAssistanceFrom
Indicates that one entity actively requested help, support, or guidance from another entity.
-
E.
canAssistIn
Indicates that one entity has the ability or capacity to help another entity perform, achieve, or carry out a particular task, goal, or activity.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6f37f36ac8190b1bff8711d6771cb |
completed | May 3, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:35 a.m.