Triple
T7063826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Region (part) |
E164292
|
entity |
| Predicate | includedAreaFrom |
P22582
|
FINISHED |
| Object | Stirlingshire |
—
|
NE NERFINISHED |
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: Stirlingshire | Statement: [Central Region (part), includedAreaFrom, Stirlingshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedAreaFrom Context triple: [Central Region (part), includedAreaFrom, Stirlingshire]
-
A.
includesAreasOff
Indicates that something encompasses or covers areas that are turned off, inactive, or excluded from normal operation.
-
B.
includesAreaType
Indicates that one entity encompasses or contains another entity of a specified area type within its scope or boundaries.
-
C.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
D.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
E.
includesDistrict
chosen
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:38 p.m.