Triple

T10866947
Position Surface form Disambiguated ID Type / Status
Subject Digital Marketplace E256553 entity
Predicate usesProcurementModel P42886 FINISHED
Object framework agreements 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: framework agreements | Statement: [Digital Marketplace, usesProcurementModel, framework agreements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesProcurementModel
Context triple: [Digital Marketplace, usesProcurementModel, framework agreements]
  • A. procurementProgram
    Indicates a relationship where an entity is involved in organizing, managing, or participating in a structured process for acquiring goods, services, or resources.
  • B. roleInProcurement
    Indicates that an entity holds a specific role or responsibility within a procurement process or activity.
  • C. procurementMethod chosen
    Indicates the specific process or approach used to acquire goods, services, or works (e.g., open tender, direct purchase, negotiated procedure).
  • D. usesProductionModel
    Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
  • E. usesRevenueModel
    Indicates that one entity applies or operates according to a particular revenue model to generate income.
  • 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_69d6aa83d1448190a66d93c32394d21f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7516e15448190aefdba1aa635baea completed April 9, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69d70d308dfc81908792f98cfb871392 completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:20 p.m.