Triple
T8819053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishmi |
E209853
|
entity |
| Predicate | homelandTerrain |
P5378
|
FINISHED |
| Object | remote |
—
|
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: remote | Statement: [Mishmi, homelandTerrain, remote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homelandTerrain Context triple: [Mishmi, homelandTerrain, remote]
-
A.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
B.
hasHomeland
Indicates that an entity considers or recognizes a particular place or region as its homeland or place of origin.
-
C.
homelandRegion
Indicates that a region is recognized as the native or traditional homeland of a particular entity (such as a people, group, or organization).
-
D.
modernTerritoryIncludes
Indicates that the geographic area of one modern political or administrative territory fully or partially contains the geographic area of another.
-
E.
terrainFeature
chosen
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600e6e2881908934cbff0ab5d6fd |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.