Triple
T15903974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Schickele |
E385660
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | Ames, Iowa |
E201628
|
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: Ames, Iowa | Statement: [Peter Schickele, placeOfBirth, Ames, Iowa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ames, Iowa Context triple: [Peter Schickele, placeOfBirth, Ames, Iowa]
-
A.
Ames, Iowa
chosen
Ames, Iowa is a central Iowa city best known as the home of Iowa State University and a major hub for education, research, and agriculture.
-
B.
Ames
Ames is a surname of English origin borne by various notable individuals across fields such as science, politics, and the arts.
-
C.
Ames
Ames is a municipality in the autonomous community of Galicia in northwestern Spain, situated near the city of Santiago de Compostela.
-
D.
Ames, Nebraska
Ames, Nebraska is a small rural village located in Dodge County in eastern Nebraska, United States.
-
E.
Davenport, Iowa
Davenport, Iowa is a major city along the Mississippi River in eastern Iowa, known as part of the Quad Cities metropolitan area and a regional hub for commerce and culture.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563f74d88190a3d92ca0ad46e867 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf11fd1481909f460cfa4485d3e3 |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 4:52 a.m.