Triple
T11183177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Lancaster |
E264593
|
entity |
| Predicate | associatedTerritory |
P1103
|
FINISHED |
| Object | Lancaster |
E24581
|
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: Lancaster | Statement: [Earl of Lancaster, associatedTerritory, Lancaster]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lancaster Context triple: [Earl of Lancaster, associatedTerritory, Lancaster]
-
A.
Lancaster
The Lancaster is a British four-engined World War II heavy bomber renowned for its major role in night bombing campaigns and famous missions such as the "Dambusters" raid.
-
B.
Lancaster
Lancaster was the original settlement that later developed into the city of Lincoln, the capital of Nebraska.
-
C.
Lancaster
Lancaster was the original name of the city now known as Stockton in Missouri, a small Midwestern community in the United States.
-
D.
Lancaster
chosen
Lancaster is a historic city in North West England known for its medieval castle, Georgian architecture, and role as the county town of Lancashire.
-
E.
Lancaster
Lancaster is a suburban city in the Dallas–Fort Worth metropolitan area known for its residential communities and proximity to Dallas.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8a9c5e081908c85b41a268428fb |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4835928ac81909ca2addea6fc3b5f |
completed | April 19, 2026, 7:25 a.m. |
Created at: April 8, 2026, 9:29 p.m.