Triple
T27516374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Model 146 |
E694572
|
entity |
| Predicate | isBomber |
P162469
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Martin Model 146, isBomber, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBomber Context triple: [Martin Model 146, isBomber, true]
-
A.
hasBomber
Indicates that an entity possesses, controls, or is associated with a bomber aircraft.
-
B.
designedToBomb
Indicates that something was intentionally created or configured for the purpose of bombing a target.
-
C.
compatibleBomber
Indicates that one entity can function effectively as a bomber in conjunction with, or as a suitable counterpart to, another specified entity.
-
D.
bombType
Indicates the specific kind or category of bomb associated with an event, object, or action.
-
E.
mainBomberAircraft
Indicates that an entity serves as the primary bomber aircraft used by another entity (such as a military force, operation, or country).
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62efcdc40819097bcda0390571b2f |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:18 p.m.