Triple
T10470481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomorrow Never Dies |
E246909
|
entity |
| Predicate | character |
P662
|
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: [Tomorrow Never Dies, character, Q]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Q Context triple: [Tomorrow Never Dies, character, 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509305fec81908b1acd91ae1f875d |
completed | April 7, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d8a0094910819094d492c87b31898e |
completed | April 10, 2026, 7 a.m. |
Created at: April 6, 2026, 12:20 p.m.