Triple

T38145461
Position Surface form Disambiguated ID Type / Status
Subject Golf le Fleur* E952594 entity
Predicate hasAlternateRepresentation P57346 FINISHED
Object GOLF le FLEUR* 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: GOLF le FLEUR* | Statement: [Golf le Fleur*, hasAlternateRepresentation, GOLF le FLEUR*]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternateRepresentation
Context triple: [Golf le Fleur*, hasAlternateRepresentation, GOLF le FLEUR*]
  • A. hasAlternativeReferent
    Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
  • B. hasAlternativeNotation chosen
    Indicates that an entity can be represented or written in a different, equivalent form or notation.
  • C. hasAlternativeView
    Indicates that one entity presents a different or contrasting perspective, interpretation, or representation relative to another entity.
  • D. hasAlternativeBasis
    Indicates that something is supported, justified, or founded on a different underlying reason, source, or principle than the primary or original one.
  • E. hasAlternateMemberType
    Indicates that an entity is associated with a different or substitute type of member than its primary or standard member type.
  • 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_69f76f09a7148190a4b91c0bacdc127a completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fe91383a1c81909266e40c3c3ede6c completed May 9, 2026, 1:43 a.m.
PD Predicate disambiguation batch_69fe8fde094081908f0f121664fbb5c7 completed May 9, 2026, 1:37 a.m.
Created at: May 3, 2026, 4:21 p.m.