Triple
T20083020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eglon |
E500049
|
entity |
| Predicate | oppressedFor |
P136502
|
FINISHED |
| Object | 18 years |
—
|
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: 18 years | Statement: [Eglon, oppressedFor, 18 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppressedFor Context triple: [Eglon, oppressedFor, 18 years]
-
A.
socialGroupOppressed
Indicates that the social group is subjected to systemic discrimination, marginalization, or unjust treatment by more powerful groups or institutions.
-
B.
oppressionDuration
chosen
Indicates the length of time during which one entity subjects another to oppressive control, treatment, or conditions.
-
C.
discriminatedAgainst
Indicates that one entity treats another unfairly or unequally based on a particular characteristic, such as race, gender, or other protected attributes.
-
D.
persecutedIn
Indicates that an entity is subjected to oppression, harassment, or unfair treatment within a particular place, context, or time period.
-
E.
repressedDissent
Indicates that one party has actively suppressed or stifled opposition, criticism, or disagreement from another party or group.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655946f48190a6b4cb13ea4e212a |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:41 p.m.