Triple
T26893836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukrang |
E677849
|
entity |
| Predicate | reveredInRegion |
P39809
|
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: [Mukrang, reveredInRegion, Northeast India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reveredInRegion Context triple: [Mukrang, reveredInRegion, Northeast India]
-
A.
regionallyRecognizedAs
Indicates that an entity is acknowledged or designated under a specific name, status, or classification within a particular geographic region or locality.
-
B.
notableInRegion
chosen
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
C.
regionallyRecognizedBy
Indicates that an entity is officially or commonly acknowledged within a specific geographic region by a particular authority, organization, or community.
-
D.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
E.
respectedAs
Indicates that one entity regards another with esteem or honor, recognizing their value, status, or authority.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 5:46 a.m.