Triple
T7773993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Strathearn |
E179143
|
entity |
| Predicate | governingSeat |
P21613
|
FINISHED |
| Object | Strathearn region strongholds |
—
|
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: Strathearn region strongholds | Statement: [Earl of Strathearn, governingSeat, Strathearn region strongholds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingSeat Context triple: [Earl of Strathearn, governingSeat, Strathearn region strongholds]
-
A.
hasSeatOfAdministration
chosen
Indicates that an administrative body or jurisdiction has a specific place or location that serves as its central seat of governance or administration.
-
B.
countryOfJurisdiction
Indicates the country whose legal authority or jurisdiction governs or applies to a given entity, action, or arrangement.
-
C.
canonicalJurisdictionOf
Indicates that one entity holds official legal or ecclesiastical authority over another entity or domain as its recognized jurisdiction.
-
D.
governingBodyHeadquartersCountry
Indicates the country in which the headquarters of a governing body is located.
-
E.
governingBodyHeadquartersCity
Indicates the city where the headquarters of a governing body is located.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c70461b3e48190bf1e4d4f9e6bb08e |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.