Triple

T16699948
Position Surface form Disambiguated ID Type / Status
Subject Université de Lorraine E405817 entity
Predicate hasMetzSiteRole P69710 FINISHED
Object hosting engineering programs 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: hosting engineering programs | Statement: [Université de Lorraine, hasMetzSiteRole, hosting engineering programs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMetzSiteRole
Context triple: [Université de Lorraine, hasMetzSiteRole, hosting engineering programs]
  • A. hasMarketRole
    Indicates that an entity holds or performs a specific functional role within a market or marketplace context.
  • B. hasLocationRole chosen
    Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
  • C. hasNotableRoleIn
    Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
  • D. hasGlobalRole
    Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
  • E. hasLegalRole
    Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e383300d108190911e3cba8e07f2dd completed April 18, 2026, 1:12 p.m.
PD Predicate disambiguation batch_69e319bc73908190a0e38bc926b31f10 completed April 18, 2026, 5:42 a.m.
Created at: April 10, 2026, 5:19 a.m.