Triple
T8496081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Committee on Bofors |
E201102
|
entity |
| Predicate | productTypeInvestigated |
P38664
|
FINISHED |
| Object | artillery guns |
—
|
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: artillery guns | Statement: [Joint Committee on Bofors, productTypeInvestigated, artillery guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productTypeInvestigated Context triple: [Joint Committee on Bofors, productTypeInvestigated, artillery guns]
-
A.
productTypeEvaluated
Indicates that an entity’s product type has been assessed or judged according to certain criteria or standards.
-
B.
developedProductType
Indicates that an entity (such as a project, activity, or organization) has resulted in or produced a specific type of product.
-
C.
productTypeWorkedOn
chosen
Indicates that an entity has worked on or been involved in creating, developing, or handling a particular type of product.
-
D.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
-
E.
productFamily
Indicates that one product belongs to, or is categorized under, a broader product family or line.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57dbe488190af5f06faf862cd5d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.