Triple
T3564768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor 82 |
E75418
|
entity |
| Predicate | associatedWithWeaponType |
P6014
|
FINISHED |
| Object | atomic bomb |
—
|
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: atomic bomb | Statement: [Victor 82, associatedWithWeaponType, atomic bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWeaponType Context triple: [Victor 82, associatedWithWeaponType, atomic bomb]
-
A.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given context.
-
B.
hasWeaponType
chosen
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
C.
involvesWeaponType
Indicates that the relationship or action includes the use, presence, or association of a specific type or category of weapon.
-
D.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
-
E.
supportsWeapon
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0a76c008190a2056b6d990776fe |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.