Triple
T22591633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surrey parliamentary constituencies |
E564963
|
entity |
| Predicate | mapsAvailable |
P58705
|
FINISHED |
| Object | constituency boundary maps |
—
|
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: constituency boundary maps | Statement: [Surrey parliamentary constituencies, mapsAvailable, constituency boundary maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapsAvailable Context triple: [Surrey parliamentary constituencies, mapsAvailable, constituency boundary maps]
-
A.
mapsIncluded
Indicates that one map or mapping is contained within, or is a subset of, another map or mapping.
-
B.
mapsType
Indicates that one entity serves as a mapping whose values or outputs are of the specified type.
-
C.
mapAvailability
chosen
Indicates that a map is accessible or provided for use in a given context or location.
-
D.
mappingAvailableTo
Indicates that a mapping or correspondence exists and is accessible between one entity and another.
-
E.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f16160651081909d23735336fd7a16 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:49 p.m.