Triple
T37035584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tachikawa Ki-94-II |
E916623
|
entity |
| Predicate | designRevisionOf |
P35338
|
FINISHED |
| Object | earlier Ki-94 heavy fighter concept |
—
|
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: earlier Ki-94 heavy fighter concept | Statement: [Tachikawa Ki-94-II, designRevisionOf, earlier Ki-94 heavy fighter concept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designRevisionOf Context triple: [Tachikawa Ki-94-II, designRevisionOf, earlier Ki-94 heavy fighter concept]
-
A.
revisionOf
chosen
Indicates that one entity is a modified or updated version of another earlier entity.
-
B.
hasDesignChange
Indicates that an entity has undergone a modification or alteration to its original design.
-
C.
revisedVersionType
Indicates that one entity is a revised form of another, specifying the type or nature of the revision made.
-
D.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
-
E.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 3, 2026, 4:14 p.m.