Triple
T33644263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Buckland |
E861913
|
entity |
| Predicate | notableRegionOfWork |
P39809
|
FINISHED |
| Object | Chesapeake region |
E148627
|
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: Chesapeake region | Statement: [William Buckland, notableRegionOfWork, Chesapeake region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRegionOfWork Context triple: [William Buckland, notableRegionOfWork, Chesapeake region]
-
A.
notableWorkArea
Indicates the field or domain in which an entity’s significant work or contributions are primarily focused.
-
B.
notablePlaceOfWork
Indicates that there is a notable or significant place where the entity has worked or been employed.
-
C.
notableInRegion
chosen
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
D.
notableRegionOfProjects
Indicates that a region is particularly significant or prominent as the location or focus of certain projects.
-
E.
notableFromWork
Indicates that an entity is notable or well-known specifically because of a particular work it created, contributed to, or is associated with.
- F. None of above.
Provenance (4 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36271a0ab48190aca386265d5486a7 |
completed | June 20, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:42 a.m.