Triple
T18650200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hughes AN/APG-65 |
E455910
|
entity |
| Predicate | powerplantInterface |
P132890
|
FINISHED |
| Object | aircraft electrical power system |
—
|
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: aircraft electrical power system | Statement: [Hughes AN/APG-65, powerplantInterface, aircraft electrical power system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplantInterface Context triple: [Hughes AN/APG-65, powerplantInterface, aircraft electrical power system]
-
A.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
B.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
C.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
D.
powerplantExample
Indicates that one entity serves as an example or instance of a power plant in relation to another entity.
-
E.
powerplantVariant
Indicates that one power plant is a specific version, configuration, or model variant of another power plant design.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55010d27c8190aad8d3c9e8cd31b2 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:47 a.m.