Triple
T26382939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlow Bridge |
E663188
|
entity |
| Predicate | linksCounty |
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: [Marlow Bridge, linksCounty, Buckinghamshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksCounty Context triple: [Marlow Bridge, linksCounty, Buckinghamshire]
-
A.
sharesCountyWith
Indicates that two entities are located within the same county jurisdiction.
-
B.
connectsCountyTown
Indicates a relationship where a county is linked or associated with a town, typically signifying that the town lies within or is administered by that county.
-
C.
associatedWithCounty
chosen
Indicates that an entity has a relationship or linkage to a specific county, such as jurisdiction, location, or administrative association.
-
D.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
E.
associatedCountyTitle
Indicates a relationship where a county is linked to or identified by a specific official title or designation.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 11:20 p.m.