Triple
T36557787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wainriders |
E901740
|
entity |
| Predicate | subjugatedPeople |
P13391
|
FINISHED |
| Object | Northmen of Rhovanion |
—
|
NE NERFINISHED |
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: Northmen of Rhovanion | Statement: [Wainriders, subjugatedPeople, Northmen of Rhovanion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjugatedPeople Context triple: [Wainriders, subjugatedPeople, Northmen of Rhovanion]
-
A.
indicatesSubjugation
Indicates that one entity is under the domination, control, or authority of another, reflecting a hierarchical power imbalance or enforced obedience.
-
B.
populationGroupEnslaved
chosen
Indicates that one population group is held in a condition of slavery or forced servitude by another.
-
C.
timeOfSubjugation
Indicates the point in time at which one entity becomes subjugated or brought under the control of another.
-
D.
subjugatedInCentury
Indicates that one entity was subjugated or brought under control during a specified century.
-
E.
eventuallySubjugatedBy
Indicates that one entity ultimately comes under the control, domination, or authority of another entity after some passage of time or sequence of events.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.