Triple
T33683779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIM-162 ESSM |
E862972
|
entity |
| Predicate | Block2Feature |
P177193
|
FINISHED |
| Object | active radar seeker |
—
|
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: active radar seeker | Statement: [RIM-162 ESSM, Block2Feature, active radar seeker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Block2Feature Context triple: [RIM-162 ESSM, Block2Feature, active radar seeker]
-
A.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
-
B.
baseFeature
Indicates that one entity serves as the fundamental or primary feature upon which another entity is built or defined.
-
C.
cellBlock
Indicates that one entity is a specific cell block or cell-block area associated with, contained within, or assigned to another entity (such as a prison, facility, or organizational unit).
-
D.
blockType
Indicates that one entity is classified as a specific type or category of block in relation to another entity.
-
E.
reconstructionFeature
Indicates that one entity serves as a feature, component, or characteristic used in the reconstruction or restoration of another entity.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:43 a.m.