Triple
T7224439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham–Grantham line |
E150341
|
entity |
| Predicate | servesSettlementType |
P2741
|
FINISHED |
| Object | market town |
—
|
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: market town | Statement: [Nottingham–Grantham line, servesSettlementType, market town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesSettlementType Context triple: [Nottingham–Grantham line, servesSettlementType, market town]
-
A.
servesSettlement
chosen
Indicates that one entity provides services or support to a particular settlement or community.
-
B.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
C.
typeOfSettlement
Indicates the specific category or classification of a settlement (e.g., city, town, village) that characterizes what kind of settlement it is.
-
D.
governsSettlementType
Indicates that an authority or administrative body exercises governing control over a particular type or category of settlement.
-
E.
settlementMode
Indicates the method or process by which a financial or transactional obligation is settled or completed between parties.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9db51888190b8463d0003f334fa |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.