Triple

T3545759
Position Surface form Disambiguated ID Type / Status
Subject Eric Bana E74991 entity
Predicate notableWork P4 FINISHED
Object Troy E77827 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: Troy | Statement: [Eric Bana, notableWork, Troy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Troy
Context triple: [Eric Bana, notableWork, Troy]
  • A. Troy chosen
    Troy is a 2004 epic historical war film loosely based on Homer's Iliad, depicting the legendary conflict between the Greeks and Trojans.
  • B. Troy
    Troy is the legendary ancient city in Asia Minor that was the focal point of the Trojan War in Greek and Roman mythology.
  • C. Troy
    Troy is a historic city in eastern New York State, known for its 19th-century architecture and role in the Industrial Revolution as a major manufacturing center.
  • D. Troy
    Troy is a small city in southeastern Alabama known for being the home of Troy University and its vibrant college-town atmosphere.
  • E. Troy
    Troy is a suburban city in Michigan known for its strong business community, shopping centers, and role as a key part of the Detroit metropolitan area.
  • 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_69ad85d33c6c819081d5ac1df13b5680 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbf77d938819095c72a88b5af644a completed March 8, 2026, 6:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69b38be29b408190a8dba8c8ae2485a4 completed March 13, 2026, 4 a.m.
Created at: March 8, 2026, 3:20 p.m.