Triple
T1498691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xue Yue |
E29744
|
entity |
| Predicate | militarySpecialization |
P7256
|
FINISHED |
| Object | land warfare |
—
|
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: land warfare | Statement: [Xue Yue, militarySpecialization, land warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militarySpecialization Context triple: [Xue Yue, militarySpecialization, land warfare]
-
A.
militaryBranchEmphasis
Indicates a relationship where a military branch is given particular focus, priority, or specialization within a broader military or organizational context.
-
B.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
militaryCharacteristic
chosen
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
D.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
E.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6f0ce988190aafab4a6e0dfd710 |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.