Triple

T17848909
Position Surface form Disambiguated ID Type / Status
Subject Fortescue River E445741 entity
Predicate hasTributary P415 FINISHED
Object Hardey River
Hardey River is a watercourse in Western Australia's Pilbara region that serves as a tributary of the larger Fortescue River system.
 E2155133 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: Hardey River | Statement: [Fortescue River, hasTributary, Hardey River]
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: Hardey River
Triple: [Fortescue River, hasTributary, Hardey River]
Generated description
Hardey River is a watercourse in Western Australia's Pilbara region that serves as a tributary of the larger Fortescue River system.

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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ffd7e2c81909a42cc7ab64e7db9 completed April 19, 2026, 8:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3885ce0324819098637757f4341951 completed June 22, 2026, 12:46 a.m.
NEDg Description generation batch_6a3889aab4208190aae74bda3f9845e1 completed June 22, 2026, 1:02 a.m.
NED2 Entity disambiguation (via description) batch_6a388a2a11848190ad9dfe71938b9771 completed June 22, 2026, 1:04 a.m.
Created at: April 10, 2026, 10:16 a.m.