Triple
T10079870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enos Loveland |
E213871
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Loveland |
E264083
|
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: Loveland | Statement: [Enos Loveland, familyName, Loveland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loveland Context triple: [Enos Loveland, familyName, Loveland]
-
A.
Loveland
Loveland is a city in northern Colorado known for its art community, sculpture parks, and proximity to the Rocky Mountains.
-
B.
Loveland, Colorado
chosen
Loveland, Colorado is a city in northern Colorado known for its art community, Valentine re-mailing tradition, and proximity to the Rocky Mountains.
-
C.
Holladay
Holladay is a suburban city in the Salt Lake City metropolitan area in northern Utah, known for its residential neighborhoods and proximity to the Wasatch Mountains.
-
D.
Milford
Milford is a small community located within Beaver County in the U.S. state of Utah.
-
E.
Milford
Milford is a small town located within Otsego County in the central region of New York State.
- 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_69ca839bf730819086900c323c9b8c95 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd031ce748190bb71189afd331979 |
completed | April 2, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2b6550da881908fd5311e7b46ef24 |
completed | April 5, 2026, 7:21 p.m. |
Created at: March 30, 2026, 9 p.m.