Triple
T37955845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokoya language |
E946860
|
entity |
| Predicate | isSpokenInHills |
P153671
|
FINISHED |
| Object | Lulubo Hills |
—
|
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: Lulubo Hills | Statement: [Lokoya language, isSpokenInHills, Lulubo Hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenInHills Context triple: [Lokoya language, isSpokenInHills, Lulubo Hills]
-
A.
isSpokenInTerrain
chosen
Indicates that a particular language or speech form is used or occurs within a specific type of terrain or geographical environment.
-
B.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
-
C.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
D.
isSpokenAround
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or entity.
-
E.
isSpokenAlongRiver
Indicates that a language or dialect is used or spoken by communities located along a particular river or river system.
- F. None of above.
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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.