Triple
T33860891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhattathiri |
E867918
|
entity |
| Predicate | traditionalCommunityAssociation |
P92386
|
FINISHED |
| Object | Brahmin |
—
|
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: Brahmin | Statement: [Bhattathiri, traditionalCommunityAssociation, Brahmin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCommunityAssociation Context triple: [Bhattathiri, traditionalCommunityAssociation, Brahmin]
-
A.
homeAssociation
Indicates a relationship where one entity is associated with, belongs to, or is linked as a home or primary place to another entity.
-
B.
hasCommunityAssociation
chosen
Indicates that an entity is linked to, affiliated with, or participates in a specific community or community-based organization.
-
C.
residentialCommunity
Indicates that an entity is a residential community where people live, such as a neighborhood, housing complex, or similar residential area.
-
D.
homeAssociationFoundedIn
Indicates the year or date when a particular home association was originally established or founded.
-
E.
centralCommunityFor
Indicates that one entity serves as the primary hub or focal community for another entity or group.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 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 1, 2026, 1:47 a.m.