Triple
T25101011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moray Council area |
E628719
|
entity |
| Predicate | hasHistoricCountyOverlapWith |
P34353
|
FINISHED |
| Object | Moray |
—
|
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: Moray | Statement: [Moray Council area, hasHistoricCountyOverlapWith, Moray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCountyOverlapWith Context triple: [Moray Council area, hasHistoricCountyOverlapWith, Moray]
-
A.
historicCountyOverlap
chosen
Indicates that two areas share a common portion of territory within the boundaries of the same historic county.
-
B.
hasHistoricCountyExtentSimilarTo
Indicates that one entity’s historic county boundaries closely resemble or match those of another entity.
-
C.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
D.
hasAssociatedHistoricCounty
Indicates that an entity is linked to a specific historic county with which it is geographically or administratively associated.
-
E.
hasHistoricCountyCore
Indicates that an entity is fundamentally based in, derived from, or primarily associated with a particular historic county as its core area.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 6:25 a.m.