Triple
T4646899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desh region |
E102192
|
entity |
| Predicate | dominantCommunity |
P58898
|
FINISHED |
| Object | Maratha community |
—
|
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: Maratha community | Statement: [Desh region, dominantCommunity, Maratha community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantCommunity Context triple: [Desh region, dominantCommunity, Maratha community]
-
A.
hasDominantSpecies
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
B.
dominantEnvironment
Indicates the primary or prevailing environment or setting in which an entity most characteristically exists, operates, or exerts influence.
-
C.
dominantClass
Indicates that one class or category holds primary authority, influence, or precedence over others within a given context.
-
D.
dominantStructure
Indicates that one structure exerts primary control, influence, or prominence over other related structures within a given context.
-
E.
dominantRegion
Indicates that one region exerts primary control, influence, or prominence over another region within a given context.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd663092cc81909308f89ee1a417e4 |
completed | March 20, 2026, 3:22 p.m. |
Created at: March 20, 2026, 1:14 p.m.