Triple
T36548109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trolls (Middle-earth) |
E901186
|
entity |
| Predicate | roleInArmies |
P9463
|
FINISHED |
| Object | shock infantry |
—
|
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: shock infantry | Statement: [Trolls (Middle-earth), roleInArmies, shock infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInArmies Context triple: [Trolls (Middle-earth), roleInArmies, shock infantry]
-
A.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
B.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
servedArmy
Indicates that an entity has performed military service in, or been a member of, a particular army.
-
D.
eraOfWarfare
Indicates a historical period characterized by significant or sustained warfare.
-
E.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01926e2f348190a632eff5c91db5e0 |
completed | May 11, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_6a01923488f4819094d79a27f4bc8ab8 |
completed | May 11, 2026, 8:24 a.m. |
Created at: May 3, 2026, 4:11 p.m.