Triple
T6865583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-125 Neva/Pechora |
E158391
|
entity |
| Predicate | designedForFeature |
P57584
|
FINISHED |
| Object | improved accuracy |
—
|
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: improved accuracy | Statement: [S-125 Neva/Pechora, designedForFeature, improved accuracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForFeature Context triple: [S-125 Neva/Pechora, designedForFeature, improved accuracy]
-
A.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
E.
isFeatureBased
Indicates that one entity is derived from, determined by, or constructed using the characteristics or attributes of another entity.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.