Triple

T10660729
Position Surface form Disambiguated ID Type / Status
Subject GoldenEye E251215 entity
Predicate featuresCharacter P626 FINISHED
Object Q E84547 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: Q | Statement: [GoldenEye, featuresCharacter, Q]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Q
Context triple: [GoldenEye, featuresCharacter, Q]
  • A. Q
    Q is a powerful, omnipotent trickster from the Q Continuum who frequently tests and torments the crew of the USS Enterprise in Star Trek: The Next Generation.
  • B. Q
    The Q is a New York City Subway service that runs along the BMT Broadway Line in Manhattan and the Brighton Line in Brooklyn, providing crosstown and interborough transit.
  • C. Q chosen
    Q is a recurring comedic character from the James Bond film series, known as the eccentric head of MI6's gadget and technology division.
  • D. QUE
    QUE is the standard abbreviation used for the Quebec Remparts, a major junior ice hockey team in the Quebec Major Junior Hockey League.
  • E. QUE
    QUE is the station code for Queen station, a public transit stop in Toronto's subway system.
  • 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_69d6aa5b0d2881909584b20efc5877f0 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6e017f97c8190b22765a6f1e6719d completed April 8, 2026, 11:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69d97a8cabc88190b430cb08ed0fc515 completed April 10, 2026, 10:32 p.m.
Created at: April 8, 2026, 9:08 p.m.