Triple
T2068564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakajima Ki-27 |
E45962
|
entity |
| Predicate | mainFrontlinePeriod |
P35162
|
FINISHED |
| Object | late 1930s |
—
|
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: late 1930s | Statement: [Nakajima Ki-27, mainFrontlinePeriod, late 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFrontlinePeriod Context triple: [Nakajima Ki-27, mainFrontlinePeriod, late 1930s]
-
A.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
B.
frontLineFeature
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
-
C.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
-
D.
frontLineChange
Indicates a change in the position or configuration of the primary boundary or leading edge between opposing sides.
-
E.
frontLineDirection
Indicates the primary orientation or bearing in which the front line of a conflict, formation, or boundary is facing or advancing.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f362f48190b1b0e560424c3aef |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb87b9fc08190a748c278ef2d7dc7 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:41 p.m.