Triple
T7816223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-South-Central Dravidian |
E181012
|
entity |
| Predicate | ancestorOf |
P369
|
FINISHED |
| Object | Pengo |
E173498
|
NE 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: Pengo | Statement: [Proto-South-Central Dravidian, ancestorOf, Pengo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pengo Context triple: [Proto-South-Central Dravidian, ancestorOf, Pengo]
-
A.
Pengo
chosen
Pengo is a Dravidian language spoken primarily by the Pengo people in parts of central India, especially in Odisha and neighboring regions.
-
B.
Penge
Penge is a suburban district in southeast London known for its Victorian architecture and proximity to Crystal Palace.
-
C.
Pego
Pego is a civil parish located within the municipality of Abrantes in central Portugal.
-
D.
Pluzz
Pluzz was France Télévisions’ former online catch-up TV and streaming platform, later succeeded by france.tv.
-
E.
The Peg
The Peg is a colloquial nickname for Winnipeg, the capital and largest city of the Canadian province of Manitoba.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf96d1f088190a1d005ffb019afe9 |
completed | March 30, 2026, 10:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb1488a2e48190924f44b46f925d87 |
completed | March 31, 2026, 12:25 a.m. |
Created at: March 30, 2026, 4:39 p.m.