Triple
T5035799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Slam bomb |
E113416
|
entity |
| Predicate | tailUnit |
P31695
|
FINISHED |
| Object | stabilizing fin assembly |
—
|
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: stabilizing fin assembly | Statement: [Grand Slam bomb, tailUnit, stabilizing fin assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailUnit Context triple: [Grand Slam bomb, tailUnit, stabilizing fin assembly]
-
A.
tailConfiguration
Indicates how the tail of an entity is arranged, structured, or positioned relative to the rest of that entity.
-
B.
principalUnitUntil
Indicates that one entity serves as the primary or principal unit for another entity up to, but not beyond, a specified point in time.
-
C.
hasTail
Indicates that an entity possesses a tail as a physical attribute.
-
D.
terminusUpper
Indicates that one entity serves as the upper or final endpoint (terminus) of another entity, such as a route, segment, or ordered structure.
-
E.
followsUnit
chosen
Indicates that one unit comes directly after or is ordered subsequent to another unit in a sequence or structure.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73b9ad488190a2a8c4da8858eb91 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.