Triple

T24063982
Position Surface form Disambiguated ID Type / Status
Subject Harb al-Miaw Yawm E596035 entity
Predicate hasDurationCharacteristic P154713 FINISHED
Object brief but intense urban fighting 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: brief but intense urban fighting | Statement: [Harb al-Miaw Yawm, hasDurationCharacteristic, brief but intense urban fighting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDurationCharacteristic
Context triple: [Harb al-Miaw Yawm, hasDurationCharacteristic, brief but intense urban fighting]
  • A. hasDurationType
    Indicates that something is associated with a specific kind or category of duration (e.g., temporary, permanent, short-term, long-term).
  • B. hasOfficialDuration
    Indicates the formally defined length of time associated with an event, process, or entity.
  • C. hasTypicalPerformanceDuration
    Indicates the usual or expected length of time that a performance or activity typically lasts.
  • D. possibleDuration
    Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
  • E. hasApproximateDuration
    Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
  • 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_69e288c25c008190850cf447940ab181 completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1da598dec8190a625309fd8f10f1d completed April 29, 2026, 10:15 a.m.
PD Predicate disambiguation batch_69f1764b1d4c8190b12590c6339c31c1 completed April 29, 2026, 3:08 a.m.
PDg Predicate description generation batch_69f1785afe3c81909be28986ffe944bf completed April 29, 2026, 3:17 a.m.
Created at: April 17, 2026, 10:39 p.m.