Triple
T26408512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whirlpool |
E663894
|
entity |
| Predicate | finalVersion |
P175299
|
FINISHED |
| Object | Whirlpool-T |
—
|
NE NERFINISHED |
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: Whirlpool-T | Statement: [Whirlpool, finalVersion, Whirlpool-T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalVersion Context triple: [Whirlpool, finalVersion, Whirlpool-T]
-
A.
finalVersionAdopted
Indicates that a proposed item, document, or decision has completed all required processes and has been formally accepted as the definitive, authoritative version.
-
B.
finalVersionYear
Indicates the year in which the final or last version of something was completed, released, or became definitive.
-
C.
finalIssue
Indicates that an issue or problem is in its last or conclusive state, with no further changes or iterations expected.
-
D.
finalValue
Indicates the resulting or ultimate value obtained after all relevant operations, changes, or calculations have been completed.
-
E.
finalAuthorialEdition
Indicates that the related work or version is the definitive, author-approved edition intended as the final form of the text.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 26, 2026, 11:36 p.m.