Triple

T10382286
Position Surface form Disambiguated ID Type / Status
Subject Battle of Metz E244669 entity
Predicate location P40 FINISHED
Object Metz E90772 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: Metz | Statement: [Battle of Metz, location, Metz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Metz
Context triple: [Battle of Metz, location, Metz]
  • A. Metz
    Metz is a small rural village located in Vernon County in western Missouri, United States.
  • B. Metz chosen
    Metz is a historic city in northeastern France known for its Gothic Saint-Stephen Cathedral, Roman and medieval heritage, and role as the capital of the Moselle department in the Grand Est region.
  • C. Metz Métropole
    Metz Métropole is an intercommunal metropolitan authority in northeastern France that coordinates urban planning, economic development, and public services for Metz and its surrounding municipalities.
  • D. Maubeuge
    Maubeuge is a fortified industrial town in northern France near the Belgian border, historically significant for its strategic military position.
  • E. Bois-le-Duc
    Bois-le-Duc is the French name for ’s-Hertogenbosch, a historic Dutch city known for its medieval architecture and cultural heritage in the southern Netherlands.
  • 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_69d381b5116081908d85227bab6d3c0c completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e992d8e08190aaa9a04925f52ccc completed April 7, 2026, 11:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69d998671c1c8190be2012a3faf6ba35 completed April 11, 2026, 12:40 a.m.
Created at: April 6, 2026, 12:04 p.m.