Triple

T32520537
Position Surface form Disambiguated ID Type / Status
Subject FOD E831168 entity
Predicate equivalentFrenchExpansion P91232 FINISHED
Object Service public fédéral NE NERFINISHED

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: Service public fédéral | Statement: [FOD, equivalentFrenchExpansion, Service public fédéral]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: equivalentFrenchExpansion
Context triple: [FOD, equivalentFrenchExpansion, Service public fédéral]
  • A. isFrancophoneCounterpartOf chosen
    Indicates that one entity serves as the French-speaking or French-language equivalent or counterpart of another entity.
  • B. FrenchObjective
    Indicates that an entity serves as the goal, target, or object of an action or relation specifically within a French linguistic or contextual framework.
  • C. equivalentIn
    Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
  • D. approximateStrengthFrancoSpanish
    Indicates an estimated or inferred level of strength or intensity in the relationship or interaction between Franco and Spanish entities.
  • E. containsFrenchPhrases
    Indicates that the subject includes one or more phrases expressed in the French language.
  • 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_69f34923e1548190be0524205d8cdf8f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f7051ad6e4819095e82bbd64761803 completed May 3, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69f700fe24e08190998e2c96fbaaad38 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1 a.m.