Triple
T3655463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instrument of Accession |
E77517
|
entity |
| Predicate | scopeOfPowers |
P31477
|
FINISHED |
| Object | defence |
—
|
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: defence | Statement: [Instrument of Accession, scopeOfPowers, defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfPowers Context triple: [Instrument of Accession, scopeOfPowers, defence]
-
A.
scopeOfPower
chosen
Indicates the range or extent of authority, control, or decision-making power that an entity is permitted to exercise.
-
B.
constitutionalPower
Indicates that an entity holds authority or rights granted and defined by a constitution in relation to another entity or domain of action.
-
C.
constitutionalPowersExercisedBy
Indicates that certain powers or authorities defined by a constitution are carried out or exercised by a specified actor or institution.
-
D.
separationOfPowersWith
Indicates a constitutional or institutional arrangement in which powers and responsibilities are divided and balanced between the linked entities to prevent concentration of authority.
-
E.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3baf57c8190b72b5d1b910d9db6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.