Triple
T8661735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi J2M |
E205562
|
entity |
| Predicate | originatingService |
P83950
|
FINISHED |
| Object | Imperial Japanese Navy fighter program |
—
|
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: Imperial Japanese Navy fighter program | Statement: [Mitsubishi J2M, originatingService, Imperial Japanese Navy fighter program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingService Context triple: [Mitsubishi J2M, originatingService, Imperial Japanese Navy fighter program]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
originatingCompany
Indicates the company from which something (such as a product, document, transaction, or request) originally comes or is issued.
-
C.
originalServiceBranch
Indicates the military or organizational service branch in which an individual initially served or was first enlisted.
-
D.
serviceModuleOrigin
Indicates the original source or provider from which a service module is derived or obtained.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc487147248190b5f1bff836a11e68 |
completed | March 31, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:30 p.m.