Triple

T18279590
Position Surface form Disambiguated ID Type / Status
Subject Sandown endurance races E437828 entity
Predicate hasStrategicElement P115670 FINISHED
Object fuel strategy 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: fuel strategy | Statement: [Sandown endurance races, hasStrategicElement, fuel strategy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStrategicElement
Context triple: [Sandown endurance races, hasStrategicElement, fuel strategy]
  • A. hasStrategicFunction
    Indicates that an entity serves a planned, goal-oriented role or purpose within a broader strategy or system.
  • B. hasStrategicPass
    Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
  • C. hasStrategicPort
    Indicates that an entity possesses or controls a port that is important for strategic, military, or economic purposes.
  • D. hasStrategicContext chosen
    Indicates that something is associated with or situated within a broader strategic framework, plan, or set of objectives.
  • E. isStrategicWeapon
    Indicates that the weapon is designed or classified for large-scale, long-range, or high-impact strategic use rather than for tactical or localized operations.
  • 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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50054d1dc8190b31d02f617256e9d completed April 19, 2026, 4:18 p.m.
PD Predicate disambiguation batch_69e44fd81c788190b08c6be3b07a08c5 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:34 a.m.