Triple
T36511364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky Ilya Muromets |
E899914
|
entity |
| Predicate | firstUsedAsBomber |
P204909
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Sikorsky Ilya Muromets, firstUsedAsBomber, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedAsBomber Context triple: [Sikorsky Ilya Muromets, firstUsedAsBomber, 1914]
-
A.
hasBomber
Indicates that an entity possesses, controls, or is associated with a bomber aircraft.
-
B.
mainBomberAircraft
Indicates that an entity serves as the primary bomber aircraft used by another entity (such as a military force, operation, or country).
-
C.
numberOfBomberDeaths
Indicates the quantity of individuals who died while serving as bombers in a given context or event.
-
D.
isBomber
Indicates that an entity functions as or is classified as a bomber, typically designed or used to deliver explosive ordnance.
-
E.
firstVbomberInService
Indicates that the subject is the first V-bomber aircraft to enter operational service among a set or class of V-bombers.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.