Triple

T9890799
Position Surface form Disambiguated ID Type / Status
Subject Quadrilateral Security Dialogue E181443 entity
Predicate hasWorkingGroupOn P85663 FINISHED
Object vaccines 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: vaccines | Statement: [Quadrilateral Security Dialogue, hasWorkingGroupOn, vaccines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWorkingGroupOn
Context triple: [Quadrilateral Security Dialogue, hasWorkingGroupOn, vaccines]
  • A. hasWorkingGroupReport
    Indicates that an entity is associated with, or has produced, a report generated by a working group.
  • B. workingGroup
    Indicates that multiple entities collaborate as a designated team or committee to work together toward a shared task, project, or objective.
  • C. relatedWorkingGroup chosen
    Indicates that there is an associated or connected working group that is relevant to or involved with the referenced entity or activity.
  • D. hasWorkOn
    Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
  • E. usesGroup
    Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
  • 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_69ca8283a6708190801af7a25a7ebb9f completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cdb47dfa908190884e96e5e5d6f41f completed April 2, 2026, 12:12 a.m.
PD Predicate disambiguation batch_69cd1d872d50819096b7ab166a8decf1 completed April 1, 2026, 1:28 p.m.
Created at: March 30, 2026, 8:39 p.m.