Triple
T26309177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of Difficulty |
E661770
|
entity |
| Predicate | typeOfHardship |
P79346
|
FINISHED |
| Object | economic hardship |
—
|
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: economic hardship | Statement: [Army of Difficulty, typeOfHardship, economic hardship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHardship Context triple: [Army of Difficulty, typeOfHardship, economic hardship]
-
A.
hardshipFeature
chosen
Indicates that something possesses a characteristic, condition, or aspect that contributes to or exemplifies hardship.
-
B.
hardship
Indicates that an entity is experiencing or causing significant difficulty, suffering, or adverse conditions.
-
C.
typeOfReliefAtIssue
Indicates the specific kind or category of legal relief or remedy that is being sought or contested in a given matter.
-
D.
hasEconomicChallenge
Indicates that an entity is experiencing or facing a financial or economic difficulty, constraint, or problem.
-
E.
hasSocioeconomicIssue
Indicates that an entity is affected by, associated with, or involved in a socioeconomic problem or challenge.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 26, 2026, 10:21 p.m.