Triple

T34880461
Position Surface form Disambiguated ID Type / Status
Subject Dally Messenger E1005995 entity
Predicate parent P120 FINISHED
Object Charles Amos Messenger
Charles Amos Messenger was an Australian riverboat captain and hotelier known for his work on the Murray River and as the father of rugby league pioneer Dally Messenger.
E2115103 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: Charles Amos Messenger | Statement: [Dally Messenger, parent, Charles Amos Messenger]
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: Charles Amos Messenger
Triple: [Dally Messenger, parent, Charles Amos Messenger]
Generated description
Charles Amos Messenger was an Australian riverboat captain and hotelier known for his work on the Murray River and as the father of rugby league pioneer Dally Messenger.

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_69f76dbde1c08190a24e7f9beb564c8d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7819ff8948190a44aea9724590c6d completed May 3, 2026, 5:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37796ae15c8190a835922d437c3299 completed June 21, 2026, 5:40 a.m.
NEDg Description generation batch_6a377a6cd7c48190aa8d76a19cd6ef4e completed June 21, 2026, 5:45 a.m.
NED2 Entity disambiguation (via description) batch_6a377b124f288190a861cdacfbbc0b5d completed June 21, 2026, 5:48 a.m.
Created at: May 3, 2026, 4 p.m.