Triple
T9192376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aslian branch |
E220620
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Lanoh |
E783471
|
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: Lanoh | Statement: [Aslian branch, hasLanguage, Lanoh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lanoh Context triple: [Aslian branch, hasLanguage, Lanoh]
-
A.
Lanoh
chosen
Lanoh is an indigenous Aslian language spoken by a small Orang Asli community in Peninsular Malaysia.
-
B.
Tayauh
Tayauh was a participant in the Tepanec War, a conflict among pre-Columbian Nahua city-states in central Mexico.
-
C.
Nawuli
Nawuli is an alternative name for the Nawuri language, a Guang language spoken primarily in parts of Ghana.
-
D.
Loinang
Loinang is an alternative name for the Saluan language, an Austronesian language spoken in Central Sulawesi, Indonesia.
-
E.
Lamani
Lamani refers to the Lambadi (or Banjara) community, a traditionally nomadic tribal group in India known for their vibrant culture, distinctive dress, and rich folk traditions.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5c077b4819086c74e91ee4bd75e |
completed | April 1, 2026, 8:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d065d5e81c8190b6687999a87fd559 |
completed | April 4, 2026, 1:13 a.m. |
Created at: March 30, 2026, 7:24 p.m.