Triple
T17290690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMK heavy tank prototype |
E419774
|
entity |
| Predicate | designEvaluation |
P41290
|
FINISHED |
| Object | insufficient mobility |
—
|
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: insufficient mobility | Statement: [SMK heavy tank prototype, designEvaluation, insufficient mobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designEvaluation Context triple: [SMK heavy tank prototype, designEvaluation, insufficient mobility]
-
A.
evaluationAspect
Indicates the specific dimension or criterion of performance or quality that is being assessed within an evaluation.
-
B.
evaluationModel
Indicates a relationship where one entity serves as a model, standard, or framework used to assess, judge, or measure the performance or quality of another entity.
-
C.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
D.
designStatus
Indicates the current state or phase of progress for a design within its lifecycle.
-
E.
designIssue
chosen
Indicates that there is a problem, flaw, or concern related to the design of an entity or 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e437837d048190949b947f5437636d |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.