Triple
T37608324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roh |
E935715
|
entity |
| Predicate | linkedToEthnogenesisOf |
P157736
|
FINISHED |
| Object | Rohilla people |
—
|
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: Rohilla people | Statement: [Roh, linkedToEthnogenesisOf, Rohilla people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToEthnogenesisOf Context triple: [Roh, linkedToEthnogenesisOf, Rohilla people]
-
A.
ethnogenesisOf
Indicates the process or relationship by which a particular group, culture, or people comes into existence or forms its distinct identity.
-
B.
ethnogenesisInfluencedBy
chosen
Indicates that the process of formation or emergence of an ethnic group was shaped or affected by a specified factor or agent.
-
C.
ethnogenesisRegion
Indicates the geographic region where the formation or emergence of an ethnic group took place.
-
D.
ethnogenesisDebate
Indicates a scholarly or ideological dispute over how a particular ethnic group originated, formed, or came to be recognized.
-
E.
ethnogenesisInCentury
Indicates the century during which a particular ethnic group or people came into existence or was formed.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 3, 2026, 4:18 p.m.