Triple
T31225351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missile Mer-Mer 40 |
E796119
|
entity |
| Predicate | terminalPhase |
P44658
|
FINISHED |
| Object | active radar homing 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 homing seeker | Statement: [Missile Mer-Mer 40, terminalPhase, active radar homing seeker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalPhase Context triple: [Missile Mer-Mer 40, terminalPhase, active radar homing seeker]
-
A.
phase2Terminus
Indicates that an entity serves as the endpoint or final state of a second phase in a multi-phase process or sequence.
-
B.
finalPhaseOf
chosen
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
C.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
D.
terminateIn
Indicates that one entity ends, concludes, or comes to a stop within, at, or because of another entity or condition.
-
E.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 9:10 p.m.