Triple
T1109995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PV-12 |
E25571
|
entity |
| Predicate | powerTransmission |
P4163
|
FINISHED |
| Object | propeller drive |
—
|
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: propeller drive | Statement: [PV-12, powerTransmission, propeller drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerTransmission Context triple: [PV-12, powerTransmission, propeller drive]
-
A.
transmission
chosen
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
B.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
C.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
-
D.
electrificationSystem
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
E.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4ba045fd88190982e1c6278fb9ca3 |
completed | March 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69a4b749e2a881909ef28745a7d2d917 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.