Triple

T210356
Position Surface form Disambiguated ID Type / Status
Subject Rectors’ Advisory Group E4702 entity
Predicate providesInputTo P1993 FINISHED
Object Coimbra Group decision-making 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: Coimbra Group decision-making | Statement: [Rectors’ Advisory Group, providesInputTo, Coimbra Group decision-making]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: providesInputTo
Context triple: [Rectors’ Advisory Group, providesInputTo, Coimbra Group decision-making]
  • A. connectsTo
    Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
  • B. providedFor
    Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
  • C. produces
    Indicates that one entity creates, generates, or yields another entity as a result or output.
  • D. contributeTo chosen
    Indicates that one entity provides support, resources, or effort that helps bring about, enhance, or maintain another entity, outcome, or state.
  • E. isAssociatedWith
    Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
  • 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_69a2575cb1dc8190a01ad332426dc339 completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25d35aa288190966b6e15af1525cb completed Feb. 28, 2026, 3:12 a.m.
PD Predicate disambiguation batch_69a25b4f71b88190866c8262922ae204 completed Feb. 28, 2026, 3:04 a.m.
Created at: Feb. 28, 2026, 2:52 a.m.