Triple
T5561499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APL New Horizons bus |
E145775
|
entity |
| Predicate | powerSystemType |
P44389
|
FINISHED |
| Object | RTG-based 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: RTG-based power system | Statement: [APL New Horizons bus, powerSystemType, RTG-based power system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSystemType Context triple: [APL New Horizons bus, powerSystemType, RTG-based power system]
-
A.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
B.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
C.
electrificationSystem
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
D.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
E.
hasPowerSupplyType
chosen
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02019c6748190aeefb86f489f726a |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.