Triple

T32315589
Position Surface form Disambiguated ID Type / Status
Subject Moorabbin Oval E825622 entity
Predicate alsoKnownAs P39 FINISHED
Object Linton Street Oval
Linton Street Oval is an Australian rules football ground in Moorabbin, Victoria, best known as the traditional home of the St Kilda Football Club.
E2002539 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: Linton Street Oval | Statement: [Moorabbin Oval, alsoKnownAs, Linton Street Oval]
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: Linton Street Oval
Triple: [Moorabbin Oval, alsoKnownAs, Linton Street Oval]
Generated description
Linton Street Oval is an Australian rules football ground in Moorabbin, Victoria, best known as the traditional home of the St Kilda Football Club.

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_69f3491213b88190a57094d8697a7455 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bdba43648190900f1020d6f7861d completed May 3, 2026, 3:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a305719d51c8190872a5aead111c1d3 completed June 15, 2026, 7:48 p.m.
NEDg Description generation batch_6a31b25563188190a03c27ce33657b96 completed June 16, 2026, 8:30 p.m.
NED2 Entity disambiguation (via description) batch_6a31b603baf88190b24834df8d6ab728 completed June 16, 2026, 8:45 p.m.
Created at: May 1, 2026, 12:46 a.m.