Triple
T8443338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of Design |
E199602
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Ames |
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 | Statement: [College of Design, city, Ames]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ames Context triple: [College of Design, city, Ames]
-
A.
Ames
Ames is a surname of English origin borne by various notable individuals across fields such as science, politics, and the arts.
-
B.
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.
-
C.
Ames, Nebraska
Ames, Nebraska is a small rural village located in Dodge County in eastern Nebraska, United States.
-
D.
Davenport
Davenport is an English surname of Norman origin that has been borne by various notable figures in mathematics, politics, and the arts.
-
E.
Davenport
Davenport is a historic community in Toronto, Ontario, known for its early settlement along Davenport Road and its role in the city’s industrial and residential development.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe310d8e08190b871bda79acde678 |
completed | March 31, 2026, 3:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4dc984ec8190910e25f36d538928 |
completed | April 2, 2026, 11:06 a.m. |
Created at: March 30, 2026, 6:08 p.m.