Triple
T21142011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/APS-145 |
E520954
|
entity |
| Predicate | replacedOnPlatformBy |
P143023
|
FINISHED |
| Object | AN/APY-9 on E-2D Advanced Hawkeye |
—
|
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: AN/APY-9 on E-2D Advanced Hawkeye | Statement: [AN/APS-145, replacedOnPlatformBy, AN/APY-9 on E-2D Advanced Hawkeye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedOnPlatformBy Context triple: [AN/APS-145, replacedOnPlatformBy, AN/APY-9 on E-2D Advanced Hawkeye]
-
A.
replacedPlatform
Indicates that one platform has been superseded or taken over by another platform.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
developedAsReplacementFor
Indicates that one entity was created or designed specifically to take the place of another entity, serving as its successor or substitute.
-
D.
replacedByInUnity
Indicates that one entity has been superseded or substituted by another entity within the context of Unity.
-
E.
oftenReplacedBy
Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723f96cf081909d10309e08aeca93 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:57 p.m.