Triple
T10678589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Lynn Industrial Estate |
E251682
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | North Lynn |
E50635
|
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: North Lynn | Statement: [North Lynn Industrial Estate, locatedIn, North Lynn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Lynn Context triple: [North Lynn Industrial Estate, locatedIn, North Lynn]
-
A.
North Lynn
chosen
North Lynn is a residential and industrial area within the town of King’s Lynn in Norfolk, England.
-
B.
Elwell
Elwell is a masculine given name of English origin, historically used in the United States and associated with figures such as military officer Elwell Stephen Otis.
-
C.
North Stifford
North Stifford is a village and residential area within the borough of Thurrock in Essex, England.
-
D.
Dyle
Dyle is a river in central Belgium that flows through cities such as Leuven and Mechelen before joining the Rupel.
-
E.
Newtown Line
The Newtown Line was a former SEPTA commuter rail line in the Philadelphia area that once extended service beyond Fox Chase into suburban Bucks County.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fb9684e48190b2786823723cde6c |
completed | April 9, 2026, 1:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d9887e974c81908c4943339ea9a93f |
completed | April 10, 2026, 11:32 p.m. |
Created at: April 8, 2026, 9:10 p.m.