Triple

T27339741
Position Surface form Disambiguated ID Type / Status
Subject Port Melbourne Football Club E690061 entity
Predicate homeGround P890 FINISHED
Object ETU Stadium
ETU Stadium is a sports venue in Port Melbourne, Victoria, best known as the home ground of the Port Melbourne Football Club in Australian rules football competitions.
E1771374 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: ETU Stadium | Statement: [Port Melbourne Football Club, homeGround, ETU Stadium]
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: ETU Stadium
Triple: [Port Melbourne Football Club, homeGround, ETU Stadium]
Generated description
ETU Stadium is a sports venue in Port Melbourne, Victoria, best known as the home ground of the Port Melbourne Football Club in Australian rules football competitions.

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_69ef355e5b388190a8fc1eba9b4a6656 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f62ad17d30819082fd2c9dbc1f964f completed May 2, 2026, 4:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12a7d24e988190a4a8aa941876aab8 completed May 24, 2026, 7:25 a.m.
NEDg Description generation batch_6a12aa1ad69c8190812c48dc928ae7a9 completed May 24, 2026, 7:34 a.m.
NED2 Entity disambiguation (via description) batch_6a12aaa5dc08819091559fa00e0be2e0 completed May 24, 2026, 7:37 a.m.
Created at: April 27, 2026, 11:42 a.m.