Triple
T30825490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Checkley |
E785050
|
entity |
| Predicate | hasPossibleOriginPlace |
P135098
|
FINISHED |
| Object | Checkley, Staffordshire |
—
|
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: Checkley, Staffordshire | Statement: [Checkley, hasPossibleOriginPlace, Checkley, Staffordshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleOriginPlace Context triple: [Checkley, hasPossibleOriginPlace, Checkley, Staffordshire]
-
A.
hasLikelyOrigin
chosen
Indicates that one entity is inferred or believed, with some degree of uncertainty, to be the source or starting point of another entity.
-
B.
hasSettingOfOrigin
Indicates that something originates from, or was initially set in, a particular setting or environment.
-
C.
hasUncertainOrigin
Indicates that the origin or source of an entity, event, or information is unknown, unclear, or not reliably established.
-
D.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
E.
hasTypicalGeographicOrigin
Indicates that an entity is commonly or characteristically associated with originating from a particular geographic location.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 29, 2026, 8:44 p.m.