Triple

T16622151
Position Surface form Disambiguated ID Type / Status
Subject Star Trek: Nemesis E403859 entity
Predicate featuresCharacter P626 FINISHED
Object Data E302620 NE 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: Data | Statement: [Star Trek: Nemesis, featuresCharacter, Data]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Data
Context triple: [Star Trek: Nemesis, featuresCharacter, Data]
  • A. Data chosen
    Data is an android Starfleet officer in Star Trek: The Next Generation, known for his quest to understand humanity and develop emotions.
  • B. Data
    Data is a clever, gadget-obsessed member of the kids' adventure group in the 1985 film "The Goonies," known for using his homemade inventions to help his friends.
  • C. Dati
    Dati is a surname most notably associated with Rachida Dati, a prominent French politician and former Minister of Justice.
  • D. Core Data
    Core Data is Apple’s object graph and persistence framework used in macOS and iOS apps to manage and store model layer data.
  • E. Datu
    Datu is a traditional title for a chieftain or local ruler in pre-colonial Philippine societies.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d883897eb481909eaaa088ba9918d9 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3754e80ec8190b3c66b33dbc7463c completed April 18, 2026, 12:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a007db27f788190a3c57b7ea8a8a9c6 completed May 10, 2026, 12:44 p.m.
Created at: April 10, 2026, 5:17 a.m.