Triple

T24451612
Position Surface form Disambiguated ID Type / Status
Subject Coquille Indian Tribe E616553 entity
Predicate hasTribalCourt P20573 FINISHED
Object Coquille Tribal Court
The Coquille Tribal Court is the judicial branch of the Coquille Indian Tribe, responsible for interpreting tribal law and resolving legal disputes within the tribe’s jurisdiction.
E1635688 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: Coquille Tribal Court | Statement: [Coquille Indian Tribe, hasTribalCourt, Coquille Tribal Court]
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: Coquille Tribal Court
Triple: [Coquille Indian Tribe, hasTribalCourt, Coquille Tribal Court]
Generated description
The Coquille Tribal Court is the judicial branch of the Coquille Indian Tribe, responsible for interpreting tribal law and resolving legal disputes within the tribe’s jurisdiction.

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_69e2d7edca608190aafefc8877a1b4da completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2985848748190ae0e436b2e83f249 completed April 29, 2026, 11:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fe386e34c8190959dca22955d6163 completed May 22, 2026, 5:03 a.m.
NEDg Description generation batch_6a0fe63a644881908dc626337f2bbc4d completed May 22, 2026, 5:14 a.m.
NED2 Entity disambiguation (via description) batch_6a0fe6898d848190ac01c7ad7c1185f8 completed May 22, 2026, 5:15 a.m.
Created at: April 18, 2026, 2:18 a.m.