Triple
T10624713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ever Glory |
E250292
|
entity |
| Predicate | hasOnboardPower |
P8164
|
FINISHED |
| Object | auxiliary diesel generators |
—
|
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: auxiliary diesel generators | Statement: [Ever Glory, hasOnboardPower, auxiliary diesel generators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardPower Context triple: [Ever Glory, hasOnboardPower, auxiliary diesel generators]
-
A.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
-
B.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
C.
hasOnboardFeature
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
-
D.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
E.
hasOnboardComputer
Indicates that one entity is equipped with or contains an onboard computer system.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7fe9fc81908b3b8d1dc06a829c |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:53 p.m.