Triple
T833230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Friday Agreement |
E18012
|
entity |
| Predicate | createsInstitutionType |
P8533
|
FINISHED |
| Object | power-sharing executive |
—
|
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: power-sharing executive | Statement: [Good Friday Agreement, createsInstitutionType, power-sharing executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsInstitutionType Context triple: [Good Friday Agreement, createsInstitutionType, power-sharing executive]
-
A.
typeOfInstitution
Indicates the specific kind or category of institution that an entity belongs to or is classified as.
-
B.
definesInstitution
chosen
Indicates that one entity formally establishes, specifies, or sets the official characteristics or structure of an institution.
-
C.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
D.
centralInstitutionOf
Indicates that one institution serves as the primary or main institutional center for another entity, such as an organization, system, or region.
-
E.
recognizedAsInstitutionBy
Indicates that an entity is acknowledged or accepted as an institution by a specified recognizing party.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb84fe081909b8f4b4202845860 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.