Triple
T19390455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Air Wing of JASDF |
E485050
|
entity |
| Predicate | isFrontlineUnit |
P136266
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [4th Air Wing of JASDF, isFrontlineUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrontlineUnit Context triple: [4th Air Wing of JASDF, isFrontlineUnit, true]
-
A.
isCombatSupportUnit
Indicates that the unit’s primary role is to provide operational or logistical support to combat forces rather than engage directly in frontline fighting.
-
B.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
-
C.
isEliteUnit
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
-
D.
isCitizenSoldierUnit
Indicates that a military unit is composed of citizen-soldiers, typically part-time or non-professional fighters drawn from the civilian population.
-
E.
hasFrontLineFeature
Indicates that an entity possesses a specific characteristic or element located on its front side or leading edge.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b44b70c81908e2f0deeabe4360f |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.