Triple

T15683456
Position Surface form Disambiguated ID Type / Status
Subject Italian cruiser Fiume E377636 entity
Predicate namedAfter P63 FINISHED
Object Fiume E225516 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: Fiume | Statement: [Italian cruiser Fiume, namedAfter, Fiume]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fiume
Context triple: [Italian cruiser Fiume, namedAfter, Fiume]
  • A. Fiume chosen
    Fiume is the historical name for the Adriatic port city now known as Rijeka, located in present-day Croatia.
  • B. Fiumana
    Fiumana is a small locality in the municipality of Predappio in the Emilia-Romagna region of northern Italy.
  • C. Riva River
    Riva River is a small river in the Beykoz district of Istanbul, Turkey, known for its scenic natural surroundings and recreational areas along its banks.
  • D. Trenta
    Trenta is a small alpine valley settlement in northwestern Slovenia, known as the scenic source area of the Soča (Isonzo) River within Triglav National Park.
  • E. Fiuminata
    Fiuminata is a small municipality in the Marche region of central Italy, known for its mountainous landscape and traditional rural character.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d85cd2e28481909d4e975bee20872f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04f31b5b881908e46ecd9fc6048ab completed April 16, 2026, 2:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffa12713588190a888d6f6dd4290e1 completed May 9, 2026, 9:03 p.m.
Created at: April 10, 2026, 4:17 a.m.