Triple

T16459839
Position Surface form Disambiguated ID Type / Status
Subject Shire of Livingstone E399777 entity
Predicate re-establishedOn P122863 FINISHED
Object 2014-01-01 LITERAL 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: 2014-01-01 | Statement: [Shire of Livingstone, re-establishedOn, 2014-01-01]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: re-establishedOn
Context triple: [Shire of Livingstone, re-establishedOn, 2014-01-01]
  • A. re-establishedAfter
    Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
  • B. reestablishedInYear
    Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
  • C. rebuiltOn
    Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
  • D. reaffirmedOn
    Indicates that a prior decision, statement, or agreement was confirmed or validated again on a specific date or occasion.
  • E. reestablishedUnderCurrentName
    Indicates that an entity previously existed under a different name and was later reestablished using its current name.
  • F. None of above. chosen

Provenance (4 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32d7ff0e881909100bb5b33c04291 completed April 18, 2026, 7:06 a.m.
PD Predicate disambiguation batch_69e227048d608190a4205eae3117629a completed April 17, 2026, 12:26 p.m.
PDg Predicate description generation batch_69e24556c1348190902a4d116c3137d9 completed April 17, 2026, 2:36 p.m.
Created at: April 10, 2026, 5:10 a.m.