Triple
T29562003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Army of the Republic |
E750060
|
entity |
| Predicate | standardArmor |
P10331
|
FINISHED |
| Object | Phase I clone trooper armor |
—
|
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: Phase I clone trooper armor | Statement: [Grand Army of the Republic, standardArmor, Phase I clone trooper armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardArmor Context triple: [Grand Army of the Republic, standardArmor, Phase I clone trooper armor]
-
A.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
B.
hasTypicalArmor
chosen
Indicates that an entity normally wears or is equipped with a standard or characteristic type of armor.
-
C.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
D.
notableArmor
Indicates that an entity is recognized for possessing or being associated with armor of particular significance, prominence, or distinction.
-
E.
designedArmor
Indicates that one entity created or planned the armor used or worn by another entity.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 5:20 p.m.