Triple
T28842621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meenas |
E728360
|
entity |
| Predicate | traditionalSocialRole |
P143209
|
FINISHED |
| Object | village headmen |
—
|
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: village headmen | Statement: [Meenas, traditionalSocialRole, village headmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSocialRole Context triple: [Meenas, traditionalSocialRole, village headmen]
-
A.
traditionalSocialClass
Indicates that an entity belongs to or is associated with a particular traditional social class within a social hierarchy.
-
B.
socioeconomicRole
Indicates the social and economic position, function, or status an entity holds within a society or system.
-
C.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
D.
socialRoleIn
chosen
Indicates that one entity holds a particular social role, status, or position within the context or framework defined by another entity.
-
E.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 28, 2026, 6:41 a.m.