Triple
T8536402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/APG-70 |
E202086
|
entity |
| Predicate | powerPlantCompatibility |
P69219
|
FINISHED |
| Object | F100-powered F-15 variants |
—
|
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: F100-powered F-15 variants | Statement: [AN/APG-70, powerPlantCompatibility, F100-powered F-15 variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerPlantCompatibility Context triple: [AN/APG-70, powerPlantCompatibility, F100-powered F-15 variants]
-
A.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
B.
powerplantTypeTested
chosen
Indicates that a specific type of power plant has been subjected to testing or evaluation.
-
C.
powerplantVariant
Indicates that one power plant is a specific version, configuration, or model variant of another power plant design.
-
D.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
E.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a3f024819095d560a205ff1c75 |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.