Triple

T4023505
Position Surface form Disambiguated ID Type / Status
Subject That Reminds Me E91334 entity
Predicate hasAmbiguityType P31777 FINISHED
Object multiple creative works share this title 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: multiple creative works share this title | Statement: [That Reminds Me, hasAmbiguityType, multiple creative works share this title]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAmbiguityType
Context triple: [That Reminds Me, hasAmbiguityType, multiple creative works share this title]
  • A. hasSingularityType
    Indicates that an entity possesses or is characterized by a specific type or category of singularity.
  • B. languageAmbiguity chosen
    Indicates that the meaning, interpretation, or reference of a linguistic expression is unclear or can be understood in multiple ways.
  • C. haveType
    Indicates that an entity belongs to or is classified under a specified type or category.
  • D. hasUncertainty
    Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
  • E. hasParType
    Indicates that an entity has a specific parent type or category to which it belongs.
  • 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_69aed9618b04819081750d979d2af098 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeface7a788190a0e4e549a6816f91 completed March 9, 2026, 4:52 p.m.
PD Predicate disambiguation batch_69aef8fc78ec819092d4dab88d85a141 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:35 p.m.