Triple
T32899369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumania (historical region) |
E841566
|
entity |
| Predicate | dominantPeople |
P56750
|
FINISHED |
| Object | Cumans |
—
|
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: Cumans | Statement: [Cumania (historical region), dominantPeople, Cumans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantPeople Context triple: [Cumania (historical region), dominantPeople, Cumans]
-
A.
dominantPoliticalElite
Indicates that one group or individual holds primary political power and influence over others within a given system or context.
-
B.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
C.
dominantParty
Indicates that one party in a relationship holds primary control, authority, or influence over the other.
-
D.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
E.
primaryPeople
chosen
Indicates that the referenced people are the main or most important individuals associated with a given entity, event, or context.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:19 a.m.