Triple
T26269558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suhungmung |
E657081
|
entity |
| Predicate | extendedControlOver |
P64448
|
FINISHED |
| Object | Brahmaputra valley |
—
|
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: Brahmaputra valley | Statement: [Suhungmung, extendedControlOver, Brahmaputra valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedControlOver Context triple: [Suhungmung, extendedControlOver, Brahmaputra valley]
-
A.
expandedControlOver
chosen
Indicates that one entity has increased or broadened authority, influence, or power over another entity or domain compared to a prior state.
-
B.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
C.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
-
D.
extendedTowards
Indicates that one entity is stretched or directed outward in the direction of another entity or location.
-
E.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 9:12 p.m.