Triple
T11301851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 鳳翔 |
E267612
|
entity |
| Predicate | primaryUseLateWar |
P98397
|
FINISHED |
| Object | aircrew training |
—
|
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: aircrew training | Statement: [鳳翔, primaryUseLateWar, aircrew training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseLateWar Context triple: [鳳翔, primaryUseLateWar, aircrew training]
-
A.
wartimeUse
Indicates that something is used or employed during a period of war or armed conflict.
-
B.
usedInWar
Indicates that something (such as a resource, technology, or strategy) was employed as part of military activities or conflict in a war.
-
C.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
D.
laterWarProductionFeature
Indicates that the subject possesses a characteristic or attribute specifically associated with a later phase of war-related production.
-
E.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a4aad4819097384e1b591be2e3 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.