Triple
T5760838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moot Hall, Keswick |
E127087
|
entity |
| Predicate | positionInSettlement |
P66212
|
FINISHED |
| Object | town centre |
—
|
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: town centre | Statement: [Moot Hall, Keswick, positionInSettlement, town centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSettlement Context triple: [Moot Hall, Keswick, positionInSettlement, town centre]
-
A.
positionInSet
Indicates that an entity occupies a specific position or rank within an ordered set or collection.
-
B.
isSettlementOf
Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
-
C.
settlementState
Indicates the state or status of a settlement process or transaction at a given point in time.
-
D.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- F. None of above. chosen
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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02938972c8190992149ea943f87bf |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:49 p.m.