Triple

T23988351
Position Surface form Disambiguated ID Type / Status
Subject Mario Rossi E604994 entity
Predicate hasSpecificity P154524 FINISHED
Object non-unique 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: non-unique | Statement: [Mario Rossi, hasSpecificity, non-unique]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSpecificity
Context triple: [Mario Rossi, hasSpecificity, non-unique]
  • A. requiresSpecificityFor
    Indicates that one entity or condition must be defined or described with a higher level of detail or precision in order for another entity, action, or process to be valid or applicable.
  • B. isMoreSpecificThan
    Indicates that one concept represents a narrower, more detailed, or more constrained case of another concept.
  • C. hasSpecification
    Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
  • D. hasSpecial
    Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
  • E. isSpecializedFor
    Indicates that one entity is specifically adapted, designed, or focused to perform optimally for a particular function, context, or domain associated with another entity.
  • 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_69e295463f7c8190b1c19dbd114641b9 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d38902fc8190af51cedfce1c6c13 completed April 29, 2026, 9:46 a.m.
PD Predicate disambiguation batch_69f1615994c48190a5de95d3f7e5cd0a completed April 29, 2026, 1:39 a.m.
PDg Predicate description generation batch_69f16e348b548190b76e50f9b611f76d completed April 29, 2026, 2:34 a.m.
Created at: April 17, 2026, 9:37 p.m.