Triple
T257592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Scotland |
E5468
|
entity |
| Predicate | hadDistinctInstitution |
P8996
|
FINISHED |
| Object | separate legal system |
—
|
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: separate legal system | Statement: [Kingdom of Scotland, hadDistinctInstitution, separate legal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadDistinctInstitution Context triple: [Kingdom of Scotland, hadDistinctInstitution, separate legal system]
-
A.
associatedWithInstitution
Indicates that an entity has a formal or recognized connection or affiliation with an institution.
-
B.
hasStateInstitution
Indicates that a particular state possesses, governs, or is served by a specific institution operating under its authority or within its jurisdiction.
-
C.
notableInstitution
Indicates that an institution holds particular significance, prominence, or recognition in relation to the subject.
-
D.
associatedInstitution
Indicates that an entity has a formal connection or affiliation with a particular institution.
-
E.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
- F. None of above. chosen
Provenance (4 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d703e688190bb86c69527e306f5 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b694c08819085bb4b256fa7736f |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c4b773c81908f1017f40b0bfd07 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.