Triple
T26976797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khond |
E679479
|
entity |
| Predicate | historicalPeriodOfSuppression |
P192357
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Khond, historicalPeriodOfSuppression, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfSuppression Context triple: [Khond, historicalPeriodOfSuppression, 19th century]
-
A.
historicalSuppressionBy
Indicates that one entity has actively or systematically suppressed, oppressed, or constrained another entity over a historical period.
-
B.
historicalPeriodOfRemoval
Indicates the historical time period during which an entity was removed, discontinued, or taken out of use.
-
C.
timePeriodOfCensorship
Indicates the span of time during which censorship was in effect for the related entity or content.
-
D.
suppressionYear
Indicates the year in which the referenced activity, expression, or entity was formally suppressed, halted, or forcibly discontinued.
-
E.
periodOfRepressionDocumented
Indicates that a specific time span characterized by repression has been recorded or evidenced in some form of documentation.
- F. None of above. chosen
Provenance (4 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: April 27, 2026, 6:43 a.m.