Triple

T11716196
Position Surface form Disambiguated ID Type / Status
Subject Amer Fort E278504 entity
Predicate locatedIn P40 FINISHED
Object Amer E918324 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: Amer | Statement: [Amer Fort, locatedIn, Amer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amer
Context triple: [Amer Fort, locatedIn, Amer]
  • A. Amer
    Amer is a common Arabic surname borne by various notable individuals across the Middle East and North Africa.
  • B. Amer chosen
    Amer is a historic town near Jaipur in Rajasthan, India, best known for the hilltop Amer Fort, a major example of Rajput architecture and a UNESCO World Heritage Site.
  • C. Amery
    Amery is an English surname most notably associated with a British political family, including Conservative politician Julian Amery.
  • D. Ameria
    Ameria is an ancient Umbrian town in central Italy, known today as Amelia, with significant archaeological and historical remains from pre-Roman and Roman times.
  • E. D’Amérique
    D’Amérique is a modernist artwork by French avant-garde artist Francis Picabia, reflecting his experimental approach within the Dada and early abstract movements.
  • 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_69d6aaff2ce88190b4a1e4b341ad5377 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4c10d988190842acd824135cf15 completed April 10, 2026, 7:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69ef83a9479c81909cbe63d81255a1bf completed April 27, 2026, 3:41 p.m.
Created at: April 8, 2026, 9:40 p.m.