Triple
T8691744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas B-18 Bolo |
E206306
|
entity |
| Predicate | B-18AFeature |
P65000
|
FINISHED |
| Object | revised nose with bombardier position |
—
|
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: revised nose with bombardier position | Statement: [Douglas B-18 Bolo, B-18AFeature, revised nose with bombardier position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: B-18AFeature Context triple: [Douglas B-18 Bolo, B-18AFeature, revised nose with bombardier position]
-
A.
mainBomberAircraft
Indicates that an entity serves as the primary bomber aircraft used by another entity (such as a military force, operation, or country).
-
B.
B_8
Indicates a generic binary relationship between two entities, labeled as type 8, whose specific nature is not defined by the predicate name alone.
-
C.
referredAircraftNotableFeature
chosen
Indicates that a referenced aircraft is associated with a notable or distinguishing feature.
-
D.
B_1
Indicates that one entity is the first or primary instance/member in an ordered series or group relative to another entity.
-
E.
aircraftConfigurationProduced
Indicates that a specific aircraft configuration has been manufactured or produced.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5735ffdc819094126e2698f98511 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.