Triple
T12421125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aylesbury Vale |
E296773
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Stone |
E781111
|
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: Stone | Statement: [Aylesbury Vale, contains, Stone]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stone Context triple: [Aylesbury Vale, contains, Stone]
-
A.
Stone
Stone is a market town in Staffordshire, England, known historically for its canal and brewing heritage.
-
B.
Stone
"Stone" is a track by the American rock band Alice in Chains from their album *The Devil Put Dinosaurs Here*.
-
C.
Stone
chosen
Stone is a village and civil parish in north-west Kent, England, known for its historic church and proximity to the River Thames and the town of Dartford.
-
D.
Stone
Stone is a landmark early poetry collection by Russian poet Osip Mandelstam, noted for its dense imagery and classical precision.
-
E.
Stone
Stone is a common English surname borne by numerous notable individuals across history, including figures in religion, politics, arts, and sciences.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d702b1481909db5f5bed6292ce0 |
completed | April 10, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6348ccaf88190aeb0dfb7fe1d8dec |
completed | May 2, 2026, 5:29 p.m. |
Created at: April 8, 2026, 9:55 p.m.