Triple
T29893611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Empire |
E759217
|
entity |
| Predicate | primaryInfantryUnit |
P74925
|
FINISHED |
| Object | stormtrooper |
—
|
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: stormtrooper | Statement: [the Empire, primaryInfantryUnit, stormtrooper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInfantryUnit Context triple: [the Empire, primaryInfantryUnit, stormtrooper]
-
A.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
-
B.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
C.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
D.
militaryUnitOf
chosen
Indicates that one entity is a military unit that belongs to, is part of, or is under the command or organizational structure of another entity.
-
E.
heavyAssaultUnit
Indicates a military or combat unit that is equipped and intended to perform high-damage, front-line assault operations, typically with heavy armor or weaponry.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a01ac8b4ac881908aa52079c985ddac |
completed | May 11, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_6a01aa7fa7b48190b4911aa6bcabe7eb |
completed | May 11, 2026, 10:07 a.m. |
Created at: April 29, 2026, 6:03 p.m.