Triple
T24756682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusi language |
E619305
|
entity |
| Predicate | isSpokenBy |
P2181
|
FINISHED |
| Object |
Lusi people
The Lusi people are an indigenous ethnic group of Papua New Guinea, traditionally living in coastal and island communities and maintaining distinct cultural practices and language.
|
E1805377
|
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: Lusi people | Statement: [Lusi language, isSpokenBy, Lusi people]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lusi people Triple: [Lusi language, isSpokenBy, Lusi people]
Generated description
The Lusi people are an indigenous ethnic group of Papua New Guinea, traditionally living in coastal and island communities and maintaining distinct cultural practices and language.
Provenance (5 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f41078fb788190bc6c18ed85b45049 |
completed | May 1, 2026, 2:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15d76ce2908190a8956c2d494b01f8 |
completed | May 26, 2026, 5:25 p.m. |
| NEDg | Description generation | batch_6a15d85aac10819081766d216efdceb2 |
completed | May 26, 2026, 5:28 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a15dac9497c8190b12b0088d9907ce5 |
completed | May 26, 2026, 5:39 p.m. |
Created at: April 18, 2026, 4:26 a.m.