Triple
T23333231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freedom Fighter |
E591501
|
entity |
| Predicate | usesArmamentType |
P6014
|
FINISHED |
| Object | cannons |
—
|
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: cannons | Statement: [Freedom Fighter, usesArmamentType, cannons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesArmamentType Context triple: [Freedom Fighter, usesArmamentType, cannons]
-
A.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
B.
hasWeaponType
chosen
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
C.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
D.
refersToArmamentRole
Indicates that one entity specifies or denotes the armament-related role or function associated with another entity.
-
E.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197eecc5c81908089eb43bc701196 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:16 p.m.