Triple
T22303071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumatran languages |
E551304
|
entity |
| Predicate | includeLanguage |
P2177
|
FINISHED |
| Object | Komering |
—
|
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: Komering | Statement: [Sumatran languages, includeLanguage, Komering]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Komering Context triple: [Sumatran languages, includeLanguage, Komering]
-
A.
Komering
chosen
Komering is an Austronesian language spoken by the Komering people of southern Sumatra in Indonesia.
-
B.
Komer
Komer is a surname most notably associated with Robert Komer, an American diplomat and national security official active during the Cold War era.
-
C.
Emmering
Emmering is a small municipality in Upper Bavaria, Germany, located in the Fürstenfeldbruck district west of Munich.
-
D.
Menkemaborg
Menkemaborg is a well-preserved historic Groningen manor house and former borg in the Netherlands, now serving as a museum showcasing 18th-century aristocratic life and architecture.
-
E.
Gorcumer
A Gorcumer is a resident or native of the Dutch city of Gorinchem.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1572517588190bef6f8bfb76afb19 |
completed | April 29, 2026, 12:56 a.m. |
Created at: April 16, 2026, 8:41 p.m.