Triple
T10112774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell |
E218281
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Campbel |
E218281
|
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: Campbel | Statement: [Campbell, hasVariant, Campbel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Campbel Context triple: [Campbell, hasVariant, Campbel]
-
A.
Campbell
Campbell is a small suburban city in California’s Silicon Valley, known as the original home of eBay and for its vibrant downtown and community events.
-
B.
Campbell
chosen
Campbell is a common Scottish surname historically associated with the powerful Clan Campbell of the Scottish Highlands.
-
C.
Brewster
Brewster is a coastal town on Cape Cod in Massachusetts known for its scenic beaches, historic charm, and bayside conservation lands.
-
D.
Brewster
Brewster is a small hamlet and census-designated place in Putnam County, New York, known for its historic downtown and role as a local commercial and transportation hub.
-
E.
Brewster
Brewster is an English occupational surname historically associated with brewing ale or beer.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15ed28081909a812e0634799ef8 |
completed | April 2, 2026, 2:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2cc20ff4481909cdd916e92eda2f6 |
completed | April 5, 2026, 8:54 p.m. |
Created at: March 30, 2026, 9:03 p.m.