Triple

T34409828
Position Surface form Disambiguated ID Type / Status
Subject Qantas Empire Airways E883224 entity
Predicate basedInEmpire P17699 FINISHED
Object British Empire NE NERFINISHED

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: British Empire | Statement: [Qantas Empire Airways, basedInEmpire, British Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: basedInEmpire
Context triple: [Qantas Empire Airways, basedInEmpire, British Empire]
  • A. provinceOfEmpire
    Indicates that a given province belongs to, is governed by, or forms an administrative part of a particular empire.
  • B. associatedEmpire chosen
    Indicates a relationship where one entity is linked or connected to a particular empire, typically as belonging to, originating from, or being under the influence or control of that empire.
  • C. countryOfFictionalEmpire
    Indicates the real-world country in which a fictional empire is located, originates, or is primarily associated.
  • D. foundedInEmpire
    Indicates that an entity (such as an organization, city, or institution) was established during the existence or rule of a specified empire.
  • E. heldInEmpire
    Indicates that an event, position, or status occurred or existed within the territorial or political bounds of a particular empire.
  • 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_69f349c1f2208190a09a489bb8b2719d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fefb15220081908da36aac386fa582 completed May 9, 2026, 9:15 a.m.
PD Predicate disambiguation batch_69fefa8e8ad48190a723fed81e9d64d0 completed May 9, 2026, 9:12 a.m.
Created at: May 1, 2026, 1:59 a.m.