Triple
T9526122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bouncing bomb |
E229763
|
entity |
| Predicate | relatedDesignUse |
P4831
|
FINISHED |
| Object | anti-ship weapon |
—
|
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: anti-ship weapon | Statement: [bouncing bomb, relatedDesignUse, anti-ship weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDesignUse Context triple: [bouncing bomb, relatedDesignUse, anti-ship weapon]
-
A.
designUse
chosen
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
B.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
C.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
D.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
E.
associatedWithUse
Indicates a relationship where one entity is connected to or involved in the use or utilization of another entity.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd989b529c81909ee18dd3d468c816 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:59 p.m.