Triple

T34871937
Position Surface form Disambiguated ID Type / Status
Subject Fiume adventure E1005773 entity
Predicate cityFormerlyPartOf P5057 FINISHED
Object Austria-Hungary 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: Austria-Hungary | Statement: [Fiume adventure, cityFormerlyPartOf, Austria-Hungary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityFormerlyPartOf
Context triple: [Fiume adventure, cityFormerlyPartOf, Austria-Hungary]
  • A. formerMunicipalityOf
    Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
  • B. cityPreviouslyLocatedIn
    Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
  • C. historicallyPartOf chosen
    Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
  • D. formerNameOfAreaWithin
    Indicates that one area previously had a different name while remaining within the same larger encompassing area.
  • E. hasAssociatedCityFormerName
    Indicates that an entity is linked to a city by referencing one of that city's former or historical names.
  • 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_69f76dbde1c08190a24e7f9beb564c8d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f782f4f10081908f97f6d0d2dbeec7 completed May 3, 2026, 5:16 p.m.
PD Predicate disambiguation batch_69f780ff71cc8190a67e71076fbad81a completed May 3, 2026, 5:08 p.m.
Created at: May 3, 2026, 4 p.m.