Triple
T4786470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double-Barreled Cannon |
E106490
|
entity |
| Predicate | designedToFireSimultaneously |
P58413
|
FINISHED |
| Object | two cannonballs |
—
|
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: two cannonballs | Statement: [Double-Barreled Cannon, designedToFireSimultaneously, two cannonballs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToFireSimultaneously Context triple: [Double-Barreled Cannon, designedToFireSimultaneously, two cannonballs]
-
A.
releasedSimultaneouslyWith
Indicates that two or more entities were made available or launched at the same time or on the same date.
-
B.
timeOfDetonation
Indicates the specific point in time at which a detonation event occurs.
-
C.
detonationMode
Indicates the specific manner or mechanism by which a detonation is initiated or carried out in relation to an explosive event.
-
D.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
-
E.
hasMultipleHoldersSimultaneously
Indicates that a given item, role, or resource is concurrently possessed, controlled, or occupied by more than one holder at the same time.
- F. None of above. chosen
Provenance (4 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65d8f9d881909c24340b8dc6a104 |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:22 p.m.