Triple
T6377732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.J.Res.45 |
E143505
|
entity |
| Predicate | typeOfAuthorization |
P70275
|
FINISHED |
| Object | broad authorization for use of military force |
—
|
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: broad authorization for use of military force | Statement: [S.J.Res.45, typeOfAuthorization, broad authorization for use of military force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAuthorization Context triple: [S.J.Res.45, typeOfAuthorization, broad authorization for use of military force]
-
A.
typeOfGrant
Indicates the specific category or kind of grant associated with an entity.
-
B.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
C.
authenticationType
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
-
D.
typeOfProtectedResource
Indicates the specific category or kind of resource that is being protected within a given security or access-control context.
-
E.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0683d7af881908d66d5230e1bfcb6 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:33 p.m.