Triple
T26466571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fasque, Kincardineshire |
E665781
|
entity |
| Predicate | hasCountyCurrently |
P138392
|
FINISHED |
| Object | Aberdeenshire |
—
|
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: Aberdeenshire | Statement: [Fasque, Kincardineshire, hasCountyCurrently, Aberdeenshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyCurrently Context triple: [Fasque, Kincardineshire, hasCountyCurrently, Aberdeenshire]
-
A.
hasCurrentCounty
chosen
Indicates that an entity is currently located within, administered by, or associated with a specific county.
-
B.
hasCountyEquivalentStatus
Indicates that an entity holds an administrative or legal status equivalent to that of a county within a given jurisdiction.
-
C.
hasCountyTopStatus
Indicates that an entity holds the highest or most prominent status within a specific county.
-
D.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
E.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: April 27, 2026, 12:16 a.m.