Triple
T23350841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crowborough Beacon |
E592003
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Crowborough |
—
|
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: Crowborough | Statement: [Crowborough Beacon, locatedIn, Crowborough]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Crowborough Context triple: [Crowborough Beacon, locatedIn, Crowborough]
-
A.
Crowborough
chosen
Crowborough is a small town in East Sussex, England, known for its elevated position on the High Weald and its association with Sir Arthur Conan Doyle.
-
B.
Woodnesborough
Woodnesborough is a small village and civil parish in Kent, England, known for its rural character and historic church.
-
C.
Tuckborough
Tuckborough is a prominent Hobbit settlement in the Shire, known as the ancestral home of the Took family in J.R.R. Tolkien’s Middle-earth legendarium.
-
D.
Narborough
Narborough is a village in Leicestershire, England, known as a suburban commuter settlement near Leicester with historical roots and local amenities.
-
E.
Narborough
Narborough is a village in the English county of Norfolk, known for its rural setting and historic parish character.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a1401748190b77df0a45c2aeebf |
completed | April 29, 2026, 5:41 a.m. |
Created at: April 17, 2026, 5:20 p.m.