Triple

T29522364
Position Surface form Disambiguated ID Type / Status
Subject Ebora E748968 entity
Predicate wasProvincialCenterOf P23608 FINISHED
Object Lusitania 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: Lusitania | Statement: [Ebora, wasProvincialCenterOf, Lusitania]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasProvincialCenterOf
Context triple: [Ebora, wasProvincialCenterOf, Lusitania]
  • A. usedToBeSeatOf chosen
    Indicates that an entity previously served as the official seat or administrative center of another entity, but no longer holds that status.
  • B. capitalOfProvincePreviouslyLocatedOn
    Indicates that an entity serves or served as the capital city of a province that was formerly situated in a specified location.
  • C. wasDeFactoCapitalOf
    Indicates that a place functioned in practice as the capital of a political entity, even if it was not officially designated as such.
  • D. formerCapitalOf
    Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
  • E. wasStrategicCenterIn
    Indicates that an entity functioned as a key strategic center or hub within a specified context, such as a region, period, or conflict.
  • 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_69f0bd46d99c81908ba9d01cc1dbef7d completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66d7765208190b87b1cc6d96a151c completed May 2, 2026, 9:32 p.m.
PD Predicate disambiguation batch_69f66abfdaf08190a55f14c70be6fd4d completed May 2, 2026, 9:21 p.m.
Created at: April 28, 2026, 4:42 p.m.