Triple
T7130577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Littleport |
E166174
|
entity |
| Predicate | locatedInFenlandArea |
P56312
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Littleport, locatedInFenlandArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFenlandArea Context triple: [Littleport, locatedInFenlandArea, true]
-
A.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
B.
locatedInAgriculturalRegion
Indicates that an entity is situated within a region primarily characterized by agricultural activities or land use.
-
C.
locatedInRiverDelta
Indicates that one entity is situated within the river delta region of another entity (the river).
-
D.
locatedInNationalCharacterArea
chosen
Indicates that one entity is geographically situated within the boundaries of a specified national character area.
-
E.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e66dc2388190bdec018f1cc6b20a |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:44 p.m.