Triple
T4460396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banerjee |
E98237
|
entity |
| Predicate | isAssociatedWithCommunity |
P21358
|
FINISHED |
| Object | Brahmin |
—
|
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: Brahmin | Statement: [Banerjee, isAssociatedWithCommunity, Brahmin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithCommunity Context triple: [Banerjee, isAssociatedWithCommunity, Brahmin]
-
A.
associatedCommunity
chosen
Indicates a relationship where an entity is linked or connected to a particular community with which it is involved or identified.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasRoleInCommunity
Indicates that an entity holds or performs a specific role, function, or position within a particular community.
-
D.
hasCommunityLink
Indicates that there exists an established connection or association between an entity and a community.
-
E.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35673337c8190b923159791ec27e3 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.