Triple
T15614250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BSU-49/B air-inflatable retarder |
E375371
|
entity |
| Predicate | tailLocation |
P119437
|
FINISHED |
| Object | mounted on aft end of bomb |
—
|
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: mounted on aft end of bomb | Statement: [BSU-49/B air-inflatable retarder, tailLocation, mounted on aft end of bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailLocation Context triple: [BSU-49/B air-inflatable retarder, tailLocation, mounted on aft end of bomb]
-
A.
terminalLocation
Indicates the specific terminal or endpoint location associated with an entity or process.
-
B.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
C.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
D.
targetLocation
Indicates the specific place or destination toward which an action, movement, or effect is directed.
-
E.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e83407c8190abbcd4b7fab0ff85 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:13 a.m.