Triple

T7373830
Position Surface form Disambiguated ID Type / Status
Subject British Caledonian E170073 entity
Predicate regulatorConflict P4897 FINISHED
Object UK government aviation policy in 1970s 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: UK government aviation policy in 1970s | Statement: [British Caledonian, regulatorConflict, UK government aviation policy in 1970s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatorConflict
Context triple: [British Caledonian, regulatorConflict, UK government aviation policy in 1970s]
  • A. reportedConflict
    Indicates that one party has formally reported the existence of a conflict involving another party or situation.
  • B. triggersConflict
    Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
  • C. conflictWith chosen
    Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
  • D. reasonForConflict
    Indicates that one entity is the cause, motive, or underlying issue leading to a conflict involving another entity.
  • E. supportedConflict
    Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
  • 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_69c68a5bfaac81909ce7f001dfb70c76 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1a6643c81909d626c8b6a7a11fd completed March 27, 2026, 9:07 p.m.
PD Predicate disambiguation batch_69c6f02ee3e08190a7a00c981129b22c completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:07 p.m.