Triple

T23290041
Position Surface form Disambiguated ID Type / Status
Subject Waterfront E589999 entity
Predicate screenwriter P2831 FINISHED
Object George Bruce NE NERFINISHED

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: George Bruce | Statement: [Waterfront, screenwriter, George Bruce]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: George Bruce
Context triple: [Waterfront, screenwriter, George Bruce]
  • A. George Bruce chosen
    George Bruce was a Hollywood screenwriter active in the mid-20th century, known for scripting adventure and action films.
  • B. Andrew Bruce
    Andrew Bruce is a renowned British theatrical sound designer known for his influential work on major West End and Broadway productions.
  • C. John Bruce
    John Bruce was the short-lived son and heir of Robert the Bruce, King of Scots, and his queen consort Elizabeth de Burgh.
  • D. James Gillespie
    James Gillespie was a 19th-century Texas figure, likely a politician or military leader, honored as the namesake of Gillespie County.
  • E. Alexander Scott
    Alexander Scott was a 16th-century Scottish makar (poet) known for his courtly and satirical verse in the Scots language.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d1af9d88190a0b9b5e8fa608618 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1964a4c548190bda1e85b8d316e8a completed April 29, 2026, 5:25 a.m.
Created at: April 17, 2026, 5:01 p.m.