Triple
T26602154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimasa Kachari |
E667663
|
entity |
| Predicate | scheduledTribeIn |
P32607
|
FINISHED |
| Object | Assam |
—
|
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: Assam | Statement: [Dimasa Kachari, scheduledTribeIn, Assam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledTribeIn Context triple: [Dimasa Kachari, scheduledTribeIn, Assam]
-
A.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
B.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
C.
includesTribe
chosen
Indicates that one entity contains, encompasses, or has within it a particular tribe as a member or component.
-
D.
tribeLed
Indicates that one entity serves as the leader or ruling authority over a particular tribe.
-
E.
associatedTribeActivity
Indicates a relationship where a specific activity is linked to, practiced by, or characteristic of a particular tribe.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61570d4e08190bbe6f89efc3b9b54 |
completed | May 2, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:13 a.m.