Triple
T13116813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buslingthorpe, Lincolnshire, England |
E311114
|
entity |
| Predicate | hasPostcodeDistrict |
P961
|
FINISHED |
| Object | LN3 |
E497836
|
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: LN3 | Statement: [Buslingthorpe, Lincolnshire, England, hasPostcodeDistrict, LN3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LN3 Context triple: [Buslingthorpe, Lincolnshire, England, hasPostcodeDistrict, LN3]
-
A.
LN1
LN1 is the first French high-speed rail line (LGV Sud-Est), connecting Paris to Lyon and pioneering the TGV network.
-
B.
LN
chosen
LN is the postcode area designation for Lincoln and its surrounding region in the United Kingdom.
-
C.
LNS
LNS is the commonly used abbreviation for the Laboratory for Nuclear Science, a research institution focused on advancing the understanding of nuclear and particle physics.
-
D.
LNS
LNS is the commonly used abbreviation for Lindsey Nelson Stadium, the University of Tennessee’s baseball venue in Knoxville.
-
E.
LNPA
LNPA is the commonly used abbreviation for Italy’s top professional football league, Lega Serie A.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98182011c8190a504678affbb7787 |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e28105c481908781775ba489c296 |
completed | May 3, 2026, 5:52 a.m. |
Created at: April 9, 2026, 9:06 p.m.