Triple
T25217094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson Mk II |
E631858
|
entity |
| Predicate | hasImprovementType |
P5357
|
FINISHED |
| Object | performance improvement |
—
|
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: performance improvement | Statement: [Hudson Mk II, hasImprovementType, performance improvement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImprovementType Context triple: [Hudson Mk II, hasImprovementType, performance improvement]
-
A.
hasImproved
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
B.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
C.
hasUpgrade
chosen
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
D.
hasImprovementProgram
Indicates that an entity is associated with, participates in, or is covered by a program specifically designed to improve its performance, condition, or quality.
-
E.
hasLightingImprovements
Indicates that an entity has enhancements or upgrades made to its lighting conditions or systems.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 12:59 p.m.