Triple
T25609755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foliant program |
E642014
|
entity |
| Predicate | typeOfWeaponDeveloped |
P27030
|
FINISHED |
| Object | nerve agent |
—
|
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: nerve agent | Statement: [Foliant program, typeOfWeaponDeveloped, nerve agent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWeaponDeveloped Context triple: [Foliant program, typeOfWeaponDeveloped, nerve agent]
-
A.
typeOfWeaponsProduced
chosen
Indicates the specific categories or kinds of weapons that are manufactured or produced by an entity.
-
B.
weaponOfInterest
Indicates that an entity is a weapon that is specifically relevant, notable, or targeted for attention within a given context or scenario.
-
C.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
D.
laterWeaponizedBy
Indicates that something was subsequently developed, adapted, or used as a weapon by a specified agent or group.
-
E.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 21, 2026, 4:40 p.m.