Triple
T5020794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonesfield |
E112843
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bladon |
E5311
|
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: Bladon | Statement: [Stonesfield, locatedNear, Bladon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bladon Context triple: [Stonesfield, locatedNear, Bladon]
-
A.
Bladon
chosen
Bladon is a village in Oxfordshire, England, best known as the burial place of Sir Winston Churchill.
-
B.
Broglien
A Broglien is a resident or native of the commune of Broglie in the Eure department of northern France.
-
C.
Lechmere
Lechmere is a Massachusetts Bay Transportation Authority (MBTA) light rail station in Cambridge, Massachusetts, serving the Green Line.
-
D.
Yarrowitch
Yarrowitch is a small rural locality in New South Wales, Australia, known for its agricultural landscape and proximity to national parks and natural attractions.
-
E.
Baldwyn
Baldwyn is a masculine given name and surname of Old Germanic origin, historically associated with nobility and leadership.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd736399ac8190aa38efc4b4edc6a2 |
completed | March 20, 2026, 4:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9c60de2c81908208f93a4bd0ce55 |
completed | March 21, 2026, 1:25 p.m. |
Created at: March 20, 2026, 1:36 p.m.