Triple

T20983358
Position Surface form Disambiguated ID Type / Status
Subject We'll Make It E516823 entity
Predicate isNonUnique P116230 FINISHED
Object can be used by any survivor who has unlocked it 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: can be used by any survivor who has unlocked it | Statement: [We'll Make It, isNonUnique, can be used by any survivor who has unlocked it]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNonUnique
Context triple: [We'll Make It, isNonUnique, can be used by any survivor who has unlocked it]
  • A. isNonUniqueGlobally chosen
    Indicates that the referenced item is not guaranteed to be unique across the entire global scope or system.
  • B. hasUniqueness
    Indicates that something possesses a distinctive or one-of-a-kind quality that sets it apart from others.
  • C. isUniqueWithinStandard
    Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
  • D. isUniqueTo
    Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
  • E. isUniqueWithinSystem
    Indicates that an entity exists only once and has no duplicates within the defined system or scope.
  • 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_69e0b4ffac148190bbade9f0eceb660b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fbe03244819097630333e70c4e88 completed April 21, 2026, 4:24 a.m.
PD Predicate disambiguation batch_69e5dbe6976081908abd4e9c8734bae9 completed April 20, 2026, 7:55 a.m.
Created at: April 16, 2026, 1:48 p.m.