Triple

T14547723
Position Surface form Disambiguated ID Type / Status
Subject Persistent Uniform Resource Locator E341330 entity
Predicate canIdentify P9157 FINISHED
Object digital documents 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: digital documents | Statement: [Persistent Uniform Resource Locator, canIdentify, digital documents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canIdentify
Context triple: [Persistent Uniform Resource Locator, canIdentify, digital documents]
  • A. helpsIdentify chosen
    Indicates a relationship where one entity serves to distinguish, recognize, or determine the identity or characteristics of another entity.
  • B. identifiedUsing
    Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
  • C. canRecognize
    Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
  • D. canDetermine
    Indicates that one entity has the ability or authority to find out, establish, or decide the state, value, or outcome of another entity or situation.
  • E. canIndicate
    Indicates that one entity has the potential or capacity to serve as a sign, signal, or evidence of another entity or condition.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2ebdf9481909f4d2da1ad31099c completed April 14, 2026, 9:34 p.m.
PD Predicate disambiguation batch_69de5c546c7081909e27d504ec360c5c completed April 14, 2026, 3:25 p.m.
Created at: April 10, 2026, 1:23 a.m.