Triple
T3636643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutschland class |
E77083
|
entity |
| Predicate | powerplantAdvantage |
P49739
|
FINISHED |
| Object | high fuel efficiency for long range |
—
|
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: high fuel efficiency for long range | Statement: [Deutschland class, powerplantAdvantage, high fuel efficiency for long range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplantAdvantage Context triple: [Deutschland class, powerplantAdvantage, high fuel efficiency for long range]
-
A.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
B.
powerplantVariant
Indicates that one power plant is a specific version, configuration, or model variant of another power plant design.
-
C.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
D.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
E.
powerplantRole
Indicates that one entity serves in a specific functional or operational role relative to a power plant.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3278bb8819098bbeac023410111 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:24 p.m.