Triple
T28983857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Munda |
E734623
|
entity |
| Predicate | geographicDistributionComparedTo |
P173391
|
FINISHED |
| Object | more northerly than South Munda |
—
|
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: more northerly than South Munda | Statement: [North Munda, geographicDistributionComparedTo, more northerly than South Munda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicDistributionComparedTo Context triple: [North Munda, geographicDistributionComparedTo, more northerly than South Munda]
-
A.
geographicDistribution
Indicates the spatial range or area over which something occurs, exists, or is found.
-
B.
geographicRangeType
Indicates the kind of geographic range or distribution pattern that characterizes where an entity occurs or is found.
-
C.
geographicRangeTrend
Indicates how the spatial extent or distribution area of something is changing over time (e.g., expanding, contracting, or remaining stable).
-
D.
geographicalUsage
Indicates that something is used, applied, or occurs within a particular geographic area or region.
-
E.
geographicOverlap
Indicates that two geographic areas share at least part of the same physical space or territory.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 28, 2026, 9:13 a.m.