Triple
T6837618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alston |
E157488
|
entity |
| Predicate | claimToBe |
P32091
|
FINISHED |
| Object | one of the highest market towns in England |
—
|
LITERAL 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: one of the highest market towns in England | Statement: [Alston, claimToBe, one of the highest market towns in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimToBe Context triple: [Alston, claimToBe, one of the highest market towns in England]
-
A.
claimsToBe
chosen
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
B.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
C.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
D.
claimed
Indicates that an entity has asserted or stated something as true, often without definitive proof or verification.
-
E.
definesClaim
Indicates that one entity specifies or establishes the meaning, scope, or content of another entity’s claim.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67db4008190b86b497bf6f0c73a |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.