Triple

T25842558
Position Surface form Disambiguated ID Type / Status
Subject Osborne Naval Shipyard, South Australia E650975 entity
Predicate locatedNear P294 FINISHED
Object Adelaide
Adelaide is the coastal capital city of South Australia, known for its cultural festivals, wine regions, and role as a key economic and administrative center.
E15147 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: Adelaide | Statement: [Osborne Naval Shipyard, South Australia, locatedNear, Adelaide]
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: Adelaide
Triple: [Osborne Naval Shipyard, South Australia, locatedNear, Adelaide]
Generated description
Adelaide is the coastal capital city of South Australia, known for its cultural festivals, wine regions, and role as a key economic and administrative center.

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_69e7ab38086081908f3a8e7e0c6efd83 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6023564c08190a719144479d6a1b2 completed May 2, 2026, 1:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10ec922b7c8190b5fe51ffe39bb75d completed May 22, 2026, 11:53 p.m.
NEDg Description generation batch_6a10ed930a148190b794107b779bbdfd completed May 22, 2026, 11:58 p.m.
NED2 Entity disambiguation (via description) batch_6a10efc6a0e48190a595a5025ad5c926 completed May 23, 2026, 12:07 a.m.
Created at: April 22, 2026, 7:50 a.m.