Triple
T25949189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wraith |
E653923
|
entity |
| Predicate | hasMilitaryClass |
P164186
|
FINISHED |
| Object | Wraith commander |
—
|
NE NERFINISHED |
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: Wraith commander | Statement: [Wraith, hasMilitaryClass, Wraith commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryClass Context triple: [Wraith, hasMilitaryClass, Wraith commander]
-
A.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
B.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
C.
hasMilitarySpeciality
Indicates that an entity possesses a specific military role, skill set, or area of professional expertise within the armed forces.
-
D.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
E.
hasMilitarySecurity
Indicates that an entity provides, maintains, or is responsible for military protection or defense for another entity or area.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 22, 2026, 8:43 a.m.