Triple
T9179113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Hurdes |
E220274
|
entity |
| Predicate | historicalReputationFor |
P78687
|
FINISHED |
| Object | poverty |
—
|
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: poverty | Statement: [Las Hurdes, historicalReputationFor, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalReputationFor Context triple: [Las Hurdes, historicalReputationFor, poverty]
-
A.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
B.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
-
C.
laterReputation
Indicates that an entity’s reputation or status at a later time is being referred to in relation to an earlier point or context.
-
D.
denotesReputationOf
chosen
Indicates that one entity represents, expresses, or serves as an indicator of the reputation or perceived standing of another entity.
-
E.
institutionalReputationContext
Indicates the situational or environmental factors that shape or influence an institution’s reputation.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc25064588190856c96b229d9cd60 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.