Triple

T4921830
Position Surface form Disambiguated ID Type / Status
Subject UN Security Council Resolution 425 E110482 entity
Predicate referenceURL P47307 FINISHED
Object https://undocs.org/S/RES/425(1978) 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: https://undocs.org/S/RES/425(1978) | Statement: [UN Security Council Resolution 425, referenceURL, https://undocs.org/S/RES/425(1978)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: referenceURL
Context triple: [UN Security Council Resolution 425, referenceURL, https://undocs.org/S/RES/425(1978)]
  • A. hasReferenceURL chosen
    Indicates that an entity is associated with a specific web address that serves as a reference or source of additional information about it.
  • B. articleReference
    Indicates that one entity cites, mentions, or refers to another entity within an article or written document.
  • C. relatedRFC
    Indicates that one resource or specification is connected or associated with another through a shared or relevant RFC (Request for Comments) document.
  • D. referenceClient
    Indicates that one entity serves as a client reference for another, typically used to validate or endorse the second entity’s services or capabilities.
  • E. referencePolicy
    Indicates that one entity defines rules or guidelines governing how another entity may be referred to, cited, or mentioned.
  • 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_69bd4413f9908190afcff44d7929cc4c completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ffc2ab08190992db2400562bcee completed March 20, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69bd6c3421588190ab08e92b9558042e completed March 20, 2026, 3:48 p.m.
Created at: March 20, 2026, 1:30 p.m.