Triple
T11477903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of La Verne |
E272068
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | La Verne |
E373995
|
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: La Verne | Statement: [University of La Verne, city, La Verne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: La Verne Context triple: [University of La Verne, city, La Verne]
-
A.
La Verne, California
chosen
La Verne, California is a suburban city in Los Angeles County known for its residential character and as the home of the University of La Verne.
-
B.
Claremont
Claremont is a suburb of Hobart in Tasmania, Australia, known for its residential character and proximity to the Derwent River.
-
C.
Claremont
Claremont is a historic country house and estate in Surrey, England, known for its landscaped gardens and royal connections.
-
D.
Claremont
Claremont is a residential neighbourhood within the city of Pickering in Ontario, Canada.
-
E.
Claremont
Claremont is a residential area within the City of Salford in Greater Manchester, England.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294e0fe08190b018e840146e27ca |
completed | April 9, 2026, 10:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e60434966c81909a277b6a0fd9f358 |
completed | April 20, 2026, 10:47 a.m. |
Created at: April 8, 2026, 9:36 p.m.