Triple

T24629262
Position Surface form Disambiguated ID Type / Status
Subject AC Siena E609624 entity
Predicate hasHistoricKit P156811 FINISHED
Object black-and-white striped shirt 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: black-and-white striped shirt | Statement: [AC Siena, hasHistoricKit, black-and-white striped shirt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricKit
Context triple: [AC Siena, hasHistoricKit, black-and-white striped shirt]
  • A. hasHistoricFeatures
    Indicates that something possesses characteristics, elements, or attributes of historical significance.
  • B. hasHistoricity
    Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
  • C. hasHistoryIn
    Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
  • D. hasHistoricalDetail
    Indicates that something includes or is associated with specific information about past events, contexts, or developments.
  • E. hasHistoricalEntity
    Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
  • F. None of above. chosen

Provenance (4 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_69e2c4d1d3708190a0f2dc6a3a8523bb completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f2be044d4c819094e14eda28d371a7 completed April 30, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69f2a6d0ab708190b2e3b94dd20ca76b completed April 30, 2026, 12:48 a.m.
PDg Predicate description generation batch_69f2b8b8bc5881908df49c0b07110246 completed April 30, 2026, 2:04 a.m.
Created at: April 18, 2026, 2:32 a.m.