Triple

T32581232
Position Surface form Disambiguated ID Type / Status
Subject The Royal Victoria Regiment E832791 entity
Predicate garrison P75 FINISHED
Object Victoria
Victoria is the capital city of the Australian state of Victoria and a major cultural, political, and economic center known for its historic architecture and vibrant urban life.
E224124 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: Victoria | Statement: [The Royal Victoria Regiment, garrison, Victoria]
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: Victoria
Triple: [The Royal Victoria Regiment, garrison, Victoria]
Generated description
Victoria is the capital city of the Australian state of Victoria and a major cultural, political, and economic center known for its historic architecture and vibrant urban life.

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_69f349289adc81909f4374a58ec35a39 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c669d6408190bc26dbf21f59e237 completed May 3, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3485fd372c81909c44a7ed23bd5c41 completed June 18, 2026, 11:57 p.m.
NEDg Description generation batch_6a3486747d008190a4a30a2ad7df434b completed June 18, 2026, 11:59 p.m.
NED2 Entity disambiguation (via description) batch_6a348805ad388190ae6535daeb2b6740 completed June 19, 2026, 12:06 a.m.
Created at: May 1, 2026, 1:04 a.m.