Triple
T17290674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMK heavy tank prototype |
E419774
|
entity |
| Predicate | designOutcome |
P126837
|
FINISHED |
| Object | concept considered overly complex |
—
|
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: concept considered overly complex | Statement: [SMK heavy tank prototype, designOutcome, concept considered overly complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designOutcome Context triple: [SMK heavy tank prototype, designOutcome, concept considered overly complex]
-
A.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
B.
designProcess
Indicates the sequence of actions, decisions, and iterations involved in creating, developing, or refining a design.
-
C.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
D.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designStatus
Indicates the current state or phase of progress for a design within its lifecycle.
- 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_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. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.