Triple

T23901662
Position Surface form Disambiguated ID Type / Status
Subject Cape Juby E601060 entity
Predicate historicalAdministrationCenter P80438 FINISHED
Object Tarfaya 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: Tarfaya | Statement: [Cape Juby, historicalAdministrationCenter, Tarfaya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalAdministrationCenter
Context triple: [Cape Juby, historicalAdministrationCenter, Tarfaya]
  • A. historicAdministrativeCentre chosen
    Indicates that a place served as the main administrative or governmental center for a region or jurisdiction during a past historical period.
  • B. administrativeCenterForEmpire
    Indicates that a location served as the main administrative center or capital for a particular empire.
  • C. previousAdministrativeCentreOf
    Indicates that an entity once served as the administrative centre of another entity in the past, but no longer holds that role.
  • D. historicalCenterFor
    Indicates that one entity has served as a central or focal place of historical significance, activity, or development for another entity.
  • E. historicalAdministrativeRegionName
    Indicates the name assigned to an administrative region as it existed during a specific historical period.
  • 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_69e295364a488190bcac702e9bb7f764 completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1cdde91d081908df44442a20e0fd2 completed April 29, 2026, 9:22 a.m.
PD Predicate disambiguation batch_69f1614e24b48190a1c8fb5b7c75ee0f completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:26 p.m.