Triple

T4180224
Position Surface form Disambiguated ID Type / Status
Subject Prinz-Albrecht-Straße area E86574 entity
Predicate roleInStateTerror P46944 FINISHED
Object central command location 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: central command location | Statement: [Prinz-Albrecht-Straße area, roleInStateTerror, central command location]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInStateTerror
Context triple: [Prinz-Albrecht-Straße area, roleInStateTerror, central command location]
  • A. classifiedAsTerroristBy
    Indicates that an entity has been designated or labeled as a terrorist by a specified authority, organization, or actor.
  • B. typeOfTerrorism
    Indicates a classification relationship where an act or event is identified as belonging to a specific category or type of terrorism.
  • C. roleInCrime chosen
    Indicates the specific function, responsibility, or participation an entity has within the commission of a particular crime.
  • D. terroristOrganization
    Indicates that an entity is recognized as a group that plans, supports, or carries out acts of terrorism.
  • E. roleAtD.C.United
    Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
  • 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_69aed93de98c8190ad838ce507b77c8a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af07078cb081909f64326b12522410 completed March 9, 2026, 5:44 p.m.
PD Predicate disambiguation batch_69af019155448190b19868583272513f completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:45 p.m.