Triple
T11716213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amer Fort |
E278504
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Amer (town) |
E918322
|
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 (town) | Statement: [Amer Fort, namedAfter, Amer (town)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amer (town) Context triple: [Amer Fort, namedAfter, Amer (town)]
-
A.
Amer town
chosen
Amer town is a historic settlement near Jaipur in Rajasthan, India, renowned for its hilltop Amer Fort and scenic views over Maota Lake.
-
B.
town of Amer
The town of Amer is a historic settlement near Jaipur in Rajasthan, India, known for its Rajput heritage and as the site of the famous Amber Fort.
-
C.
Ammer
The Ammer is a river in Bavaria, Germany, known for flowing through the Ammergau Alps and feeding the Ammersee.
-
D.
Ammer
The Ammer is a small river in the German state of Baden-Württemberg that flows through the university town of Tübingen and into the Neckar.
-
E.
Township of Amaranth
The Township of Amaranth is a rural municipality in south-central Ontario, Canada, characterized by its agricultural landscape and small communities within Dufferin County.
- 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.