Triple

T36190978
Position Surface form Disambiguated ID Type / Status
Subject Pallacanestro Biella E1046984 entity
Predicate hasPlayerDevelopmentReputation P195295 FINISHED
Object yes 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: yes | Statement: [Pallacanestro Biella, hasPlayerDevelopmentReputation, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlayerDevelopmentReputation
Context triple: [Pallacanestro Biella, hasPlayerDevelopmentReputation, yes]
  • A. playableReputation
    Indicates that an entity’s reputation status can be actively used or engaged with, such as being selected, controlled, or experienced within an interactive context.
  • B. haveReputation
    Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
  • C. hasQuirkyReputation
    Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
  • D. hasInUniverseReputation
    Indicates that an entity holds a particular level or type of reputation within a specified fictional or conceptual universe.
  • E. hasReputationAmong
    Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
  • F. None of above. chosen

Provenance (4 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_69f76e3d4fbc81908c159c7beeb4ce00 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fdb45537288190b6791078d4a6899f completed May 8, 2026, 10 a.m.
PD Predicate disambiguation batch_69fdb39ad96481908376d7def9fafc13 completed May 8, 2026, 9:57 a.m.
PDg Predicate description generation batch_69fdb4544b548190b8971f8055d48caa completed May 8, 2026, 10 a.m.
Created at: May 3, 2026, 4:08 p.m.