Triple
T5055901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt |
E113901
|
entity |
| Predicate | appliedFor |
P60907
|
FINISHED |
| Object | military campaigns |
—
|
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 campaigns | Statement: [Thunderbolt, appliedFor, military campaigns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedFor Context triple: [Thunderbolt, appliedFor, military campaigns]
-
A.
canApplyFor
Indicates that one entity has the eligibility or permission to submit a request or application for another entity or opportunity.
-
B.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
C.
applicantState
Indicates the current status or condition assigned to an applicant within a process or system.
-
D.
hasGrantApplicationProcess
Indicates that an entity has a defined procedure or set of steps for submitting and processing grant applications.
-
E.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd744e45588190beaa2f96bb2f41e2 |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:38 p.m.