Triple
T27955672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (CVN-80) |
E703540
|
entity |
| Predicate | hasNuclearReactor |
P186359
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [USS Enterprise (CVN-80), hasNuclearReactor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNuclearReactor Context triple: [USS Enterprise (CVN-80), hasNuclearReactor, true]
-
A.
hasNuclearReactorType
Indicates that an entity possesses or is equipped with a specific type or classification of nuclear reactor.
-
B.
hasNuclearActivity
Indicates that an entity engages in, is involved with, or possesses capabilities related to nuclear activities or operations.
-
C.
hadNuclearFacilities
Indicates that an entity possessed or operated nuclear-related installations or infrastructure.
-
D.
hasNuclearActivityType
Indicates that an entity is associated with a specific type or category of nuclear-related activity.
-
E.
hasNuclearWeapons
Indicates that the subject possesses or controls nuclear weapons.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 27, 2026, 7:27 p.m.