Triple
T20391458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-850 |
E498093
|
entity |
| Predicate | designDifferenceFromT-800 |
P130695
|
FINISHED |
| Object | upgraded power systems |
—
|
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: upgraded power systems | Statement: [T-850, designDifferenceFromT-800, upgraded power systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designDifferenceFromT-800 Context triple: [T-850, designDifferenceFromT-800, upgraded power systems]
-
A.
designDifferenceFrom
chosen
Indicates a relationship where one design is distinguished from another by specific differing features, characteristics, or structure.
-
B.
hasDifferentFrontDesigns
Indicates that the related entities possess distinct or non-identical designs on their front sides.
-
C.
hasDifferentDesignsFor
Indicates that one entity provides or uses multiple distinct designs tailored for different other entities or contexts.
-
D.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
E.
adaptationDifference
Indicates a difference or change in how two entities adapt or have adapted relative to each other.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790f8d9c819093038f6bb6f47a92 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.