Triple
T6198200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davidson, North Carolina |
E138561
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Davidson |
E138561
|
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: Davidson | Statement: [Davidson, North Carolina, hasName, Davidson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Davidson Context triple: [Davidson, North Carolina, hasName, Davidson]
-
A.
Davidson
chosen
Davidson is a small town in North Carolina known primarily as the home of Davidson College and its close-knit, college-centered community.
-
B.
Douglas
Douglas is a town in South Lanarkshire, Scotland, historically known for its association with the powerful Douglas family and its medieval castle.
-
C.
Douglas
Douglas is a masculine given name of Scottish origin that has been widely used in English-speaking countries.
-
D.
Douglas
Douglas is a small lakeside city in Allegan County, Michigan, known for its arts community and proximity to Lake Michigan beaches.
-
E.
Douglas
Douglas is a small community located on Douglas Island across from downtown Juneau in southeastern Alaska.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06251b47881909bd8d2ea37541959 |
completed | March 22, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c16f302984819089c6a17dda476a4b |
completed | March 23, 2026, 4:49 p.m. |
Created at: March 22, 2026, 4:20 p.m.