Triple

T14592135
Position Surface form Disambiguated ID Type / Status
Subject Logan City Council area E342470 entity
Predicate hasLocalGovernmentAreaClassification P101316 FINISHED
Object City 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: City | Statement: [Logan City Council area, hasLocalGovernmentAreaClassification, City]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalGovernmentAreaClassification
Context triple: [Logan City Council area, hasLocalGovernmentAreaClassification, City]
  • A. hasLocalGovernmentAreaStatus
    Indicates that an entity holds the official designation or recognition as a local government area within a defined administrative system.
  • B. hasLocalGovernmentAreaCode
    Indicates that an entity is associated with a specific local government area identified by a particular code.
  • C. hasLocalGovernmentUnitClass chosen
    Indicates that a local government unit belongs to or is categorized under a specific administrative or governmental classification.
  • D. hasLocalGovernmentAreas
    Indicates that an entity is administratively divided into, or associated with, one or more local government areas.
  • E. hasLocalGovernmentCode
    Indicates that an entity is associated with a specific code assigned by a local government authority for identification or administrative purposes.
  • F. None of above.

Provenance (3 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_69d822ddc0f081909cd8163c7de298cd completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb4249af08190962009741d1f7d41 completed April 14, 2026, 9:39 p.m.
PD Predicate disambiguation batch_69de656a953481909a4645b004c40de7 completed April 14, 2026, 4:03 p.m.
Created at: April 10, 2026, 1:24 a.m.