Triple
T7133494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Hercules |
E166247
|
entity |
| Predicate | usedInAircraftType |
P30181
|
FINISHED |
| Object | bomber aircraft |
—
|
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: bomber aircraft | Statement: [Bristol Hercules, usedInAircraftType, bomber aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAircraftType Context triple: [Bristol Hercules, usedInAircraftType, bomber aircraft]
-
A.
usedByAircraftType
chosen
Indicates that something (such as equipment, infrastructure, or a procedure) is employed or operated by a specific type or category of aircraft.
-
B.
usedOnAircraftName
Indicates that something is employed or applied on an aircraft identified by a specific name.
-
C.
usedOnAircraftRole
Indicates that something is employed or applied in the context of a specific role or function on an aircraft.
-
D.
usedInAviation
Indicates that something is employed or applied within the field or context of aviation.
-
E.
usesCarrierAircraft
Indicates that one entity employs or operates aircraft that are designed to be launched from and recovered by an aircraft carrier.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e68f15bc8190a4d82b8ee388f497 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.