Triple
T15245315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London postal region |
E364362
|
entity |
| Predicate | adminBoundaryRelation |
P117759
|
FINISHED |
| Object | does not exactly match Greater London administrative boundary |
—
|
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: does not exactly match Greater London administrative boundary | Statement: [London postal region, adminBoundaryRelation, does not exactly match Greater London administrative boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminBoundaryRelation Context triple: [London postal region, adminBoundaryRelation, does not exactly match Greater London administrative boundary]
-
A.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
B.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
C.
geographicBoundary
Indicates that one entity serves as a limiting border or edge that defines the geographic extent or separation of another entity.
-
D.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
E.
hasBoundaryUnit
Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f306f08190be448b215d6c9b6c |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.