Triple
T28155235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remenham |
E714723
|
entity |
| Predicate | traditionalCountyAffiliation |
P13451
|
FINISHED |
| Object | Buckinghamshire |
—
|
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: Buckinghamshire | Statement: [Remenham, traditionalCountyAffiliation, Buckinghamshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCountyAffiliation Context triple: [Remenham, traditionalCountyAffiliation, Buckinghamshire]
-
A.
traditionalCountyIncludes
Indicates that a traditional or historic county geographically contains or encompasses another area or entity within its boundaries.
-
B.
associatedWithCounty
chosen
Indicates that an entity has a relationship or linkage to a specific county, such as jurisdiction, location, or administrative association.
-
C.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
-
D.
associatedCountyTitle
Indicates a relationship where a county is linked to or identified by a specific official title or designation.
-
E.
associatedWithCountySeat
Indicates that an entity has a relationship or connection to a county’s administrative center or county seat.
- F. None of above.
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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 27, 2026, 10:02 p.m.