Triple
T26893821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemphu |
E677848
|
entity |
| Predicate | regionReveredIn |
P181210
|
FINISHED |
| Object | Northeast India |
—
|
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: Northeast India | Statement: [Hemphu, regionReveredIn, Northeast India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionReveredIn Context triple: [Hemphu, regionReveredIn, Northeast India]
-
A.
regionException
Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
-
B.
regionImplied
Indicates that a broader or more general region is inferred or assumed from a given, more specific regional reference.
-
C.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
D.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
E.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 27, 2026, 5:46 a.m.