Triple
T5256858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben More (Mull) |
E118720
|
entity |
| Predicate | hasPostcodeAreaNearby |
P61362
|
FINISHED |
| Object | PA |
—
|
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: PA | Statement: [Ben More (Mull), hasPostcodeAreaNearby, PA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostcodeAreaNearby Context triple: [Ben More (Mull), hasPostcodeAreaNearby, PA]
-
A.
hasPostcodeDistrictsApprox
Indicates that one entity is associated with a set of postcode districts in an approximate or non-exact manner.
-
B.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
-
C.
hasNearbySuburb
Indicates that one location has another location as a suburb situated in close geographic proximity.
-
D.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
-
E.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.