Triple
T26434590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Caithness |
E664603
|
entity |
| Predicate | jurisdictionEra |
P95180
|
FINISHED |
| Object | early modern Scotland |
—
|
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: early modern Scotland | Statement: [Earl of Caithness, jurisdictionEra, early modern Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurisdictionEra Context triple: [Earl of Caithness, jurisdictionEra, early modern Scotland]
-
A.
historicalJurisdiction
Indicates that one entity previously held legal or administrative authority over another entity during a past time period.
-
B.
jurisdictionPeriod
chosen
Indicates the time span during which a particular authority or entity holds legal or official jurisdiction over something.
-
C.
hasTemporalJurisdictionFrom
Indicates that an authority’s jurisdiction or control over something begins at a specified point in time.
-
D.
dateEnactedEraName
Indicates that a law, policy, or formal act was enacted during a specific named historical era.
-
E.
constitutionalEraName
Indicates the named historical or political era associated with a particular constitution or constitutional regime.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:52 p.m.