Triple
T16259907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karo |
E394725
|
entity |
| Predicate | relatedEthnicGroup |
P1969
|
FINISHED |
| Object | Toba Batak |
E511803
|
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: Toba Batak | Statement: [Karo, relatedEthnicGroup, Toba Batak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Toba Batak Context triple: [Karo, relatedEthnicGroup, Toba Batak]
-
A.
Toba Batak
chosen
Toba Batak is an Austronesian language spoken primarily by the Toba Batak people of North Sumatra, Indonesia.
-
B.
Tapanuli
Tapanuli is a region in northern Sumatra, Indonesia, known for its Batak cultural heritage and distinct highland landscapes.
-
C.
Toba
Toba is a coastal city in central Japan’s Mie Prefecture, known for its pearl cultivation, scenic bays, and maritime heritage.
-
D.
Toba
Toba was a 12th-century Japanese emperor of the late Heian period whose reign and later cloistered rule significantly influenced imperial politics.
-
E.
Pakpak-Dairi
Pakpak-Dairi is an Austronesian language spoken by the Pakpak (Dairi) people of northern Sumatra, Indonesia.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c3082c8190a1c9f92b255fdbb6 |
completed | April 17, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000eee110c819088d99b80435ab70b |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:04 a.m.