Triple
T14426467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Olney |
E357709
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Olney |
E127998
|
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: Olney | Statement: [Treaty of Olney, namedAfter, Olney]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Olney Context triple: [Treaty of Olney, namedAfter, Olney]
-
A.
Olney
Olney is a residential neighborhood in North Philadelphia known for its diverse population and urban character.
-
B.
Olney
chosen
Olney is a historic market town in southeast England, known for its traditional pancake race and association with the poet William Cowper.
-
C.
Olney
Olney is an English-origin surname borne by various notable individuals, including figures in law, politics, and the arts.
-
D.
Olney Manor Park
Olney Manor Park is a public recreational park in Olney, Maryland, featuring sports facilities, open green spaces, and community amenities for local residents.
-
E.
Oakington
Oakington is a village in Cambridgeshire, England, known for its rural character and proximity to the city of Cambridge.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de911398f08190be85bc0a8bef6b1b |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bcfa1d88190b59cefd3e305f55f |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.