Triple
T2251728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimitz-class aircraft carrier |
E49631
|
entity |
| Predicate | powerPlant |
P17850
|
FINISHED |
| Object | two A4W nuclear reactors |
—
|
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: two A4W nuclear reactors | Statement: [Nimitz-class aircraft carrier, powerPlant, two A4W nuclear reactors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerPlant Context triple: [Nimitz-class aircraft carrier, powerPlant, two A4W nuclear reactors]
-
A.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
B.
powerplantFor
chosen
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
C.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
D.
powerplantRole
Indicates that one entity serves in a specific functional or operational role relative to a power plant.
-
E.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11d04688190abc04fac3a1804a9 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.