Triple
T4310294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raworth |
E94054
|
entity |
| Predicate | localityType |
P31474
|
FINISHED |
| Object | residential suburb |
—
|
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: residential suburb | Statement: [Raworth, localityType, residential suburb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localityType Context triple: [Raworth, localityType, residential suburb]
-
A.
typeLocality
Indicates the specific geographic location where a specimen or taxon was originally found and formally described.
-
B.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
C.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
D.
urbanDistrictType
chosen
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
E.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d55d748190a57fabcf58782dba |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:11 p.m.