Triple
T18846079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midlothian South, Tweeddale and Lauderdale |
E460917
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Lauderdale |
—
|
NE NERFINISHED |
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: Lauderdale | Statement: [Midlothian South, Tweeddale and Lauderdale, namedAfter, Lauderdale]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lauderdale Context triple: [Midlothian South, Tweeddale and Lauderdale, namedAfter, Lauderdale]
-
A.
Lauderdale
Lauderdale is a small suburban city in Ramsey County, Minnesota, situated within the Minneapolis–Saint Paul metropolitan area.
-
B.
Lauderdale
chosen
Lauderdale is a historic district in the Scottish Borders, traditionally associated with the town of Lauder as its county town.
-
C.
Dade
Dade is a surname most notably associated with U.S. Army Major Francis L. Dade, who was killed in the Second Seminole War and for whom several places in the United States were named.
-
D.
Dade
Dade was the Chinese era name used during the reign of Temür Khan, the second emperor of the Yuan dynasty in China.
-
E.
Davie
Davie is a diminutive or affectionate form of the given name David, commonly used in English-speaking contexts.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ee96988190bf247b986777945c |
completed | April 20, 2026, 5:26 a.m. |
Created at: April 10, 2026, 11:56 a.m.