Triple

T24431392
Position Surface form Disambiguated ID Type / Status
Subject Salarians E616008 entity
Predicate CitadelCouncilSeat P83391 FINISHED
Object yes LITERAL 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: yes | Statement: [Salarians, CitadelCouncilSeat, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: CitadelCouncilSeat
Context triple: [Salarians, CitadelCouncilSeat, yes]
  • A. citadelAlsoCalled
    Indicates that a citadel is known or referred to by an alternative name or alias.
  • B. wasCitadelOf
    Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
  • C. roleInCitadel chosen
    Indicates the specific function, position, or responsibility an entity holds within a citadel or fortified complex.
  • D. seatOfPowerLocatedIn
    Indicates that the primary governing authority or central power base of an entity is situated within a specified location.
  • E. seatOfGovernment
    Indicates that a location serves as the administrative center where a government exercises its official authority and conducts its primary governing functions.
  • 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_69e2d7eadb248190a867130fe45f0388 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f29782a4a0819087cb7ba399371520 completed April 29, 2026, 11:42 p.m.
PD Predicate disambiguation batch_69f287d3237c819099559c00f83131d8 completed April 29, 2026, 10:36 p.m.
Created at: April 18, 2026, 2:16 a.m.