Triple
T26269556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suhungmung |
E657081
|
entity |
| Predicate | incorporatedGroup |
P160186
|
FINISHED |
| Object | Chutiya nobility into Ahom administration |
—
|
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: Chutiya nobility into Ahom administration | Statement: [Suhungmung, incorporatedGroup, Chutiya nobility into Ahom administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatedGroup Context triple: [Suhungmung, incorporatedGroup, Chutiya nobility into Ahom administration]
-
A.
incorporatedAs
Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
-
B.
hasCorporateGroup
Indicates that one corporate entity belongs to, or is associated with, a broader corporate group or conglomerate.
-
C.
corporateGroupType
Indicates the classification of a corporate group according to its organizational or legal type.
-
D.
companyIncorporatedIn
Indicates that a company was legally formed and registered in a specified jurisdiction or location.
-
E.
representedGroups
Indicates that an entity serves as an official or recognized representative for one or more groups.
- F. None of above. chosen
Provenance (4 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e2fb90c8190a05e458ca3cccadc |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 9:12 p.m.