Triple

T30116014
Position Surface form Disambiguated ID Type / Status
Subject Raqqa E765418 entity
Predicate controlPeriodApproximate P115721 FINISHED
Object 2013–2017 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: 2013–2017 | Statement: [Raqqa, controlPeriodApproximate, 2013–2017]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controlPeriodApproximate
Context triple: [Raqqa, controlPeriodApproximate, 2013–2017]
  • A. timePeriodApproximation chosen
    Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
  • B. activePeriodApproximate
    Indicates that the time span during which an entity was active is known only approximately rather than as precise dates.
  • C. timePeriod
    Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
  • D. rotationPeriod_hours
    Indicates the length of time, measured in hours, that an object takes to complete one full rotation on its axis.
  • E. dstPeriod
    Indicates the specific time period during which daylight saving time is in effect for a given entity or context.
  • 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_69f2247716748190ae4f16998f49ddf1 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fd485f57dc8190820365396d041991 completed May 8, 2026, 2:20 a.m.
PD Predicate disambiguation batch_69fd47d35da081908bec8901018d186c completed May 8, 2026, 2:17 a.m.
Created at: April 29, 2026, 7:12 p.m.