Triple

T1065303
Position Surface form Disambiguated ID Type / Status
Subject Book III: Polybius E22995 entity
Predicate historicalContextOfComposition P1409 FINISHED
Object late 17th century to early 18th century 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: late 17th century to early 18th century | Statement: [Book III: Polybius, historicalContextOfComposition, late 17th century to early 18th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalContextOfComposition
Context triple: [Book III: Polybius, historicalContextOfComposition, late 17th century to early 18th century]
  • A. hasHistoricalContext chosen
    Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
  • B. dateOfComposition
    Indicates the calendar date or time period when a particular work was created or composed.
  • C. historicalOrigin
    Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
  • D. historicallyConsidered
    Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
  • E. historicalReception
    Indicates how an event, work, or figure was received, interpreted, or evaluated by people and institutions over time.
  • 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_69a493dada0481909c43649f9843ea91 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b9e1047481909af1cf8df2a01fff completed March 1, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69a4b736f1e881909bace735b38c0ade completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.