Triple
T34631247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reddy |
E889294
|
entity |
| Predicate | associatedWithSocialRole |
P110783
|
FINISHED |
| Object | landowning 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: landowning community | Statement: [Reddy, associatedWithSocialRole, landowning community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSocialRole Context triple: [Reddy, associatedWithSocialRole, landowning community]
-
A.
associatedCollectiveRole
chosen
Indicates that an entity is linked to a role or function held within a collective, group, or organization.
-
B.
associatedWithUnitRole
Indicates that an entity has a connection or linkage to a specific role within a particular unit or organizational subdivision.
-
C.
socialRoleIn
Indicates that one entity holds a particular social role, status, or position within the context or framework defined by another entity.
-
D.
associatedWithCandidateRole
Indicates a relationship where an entity is linked or connected to a specific candidate role, such as a position or function under consideration.
-
E.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.