Triple
T24030995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSWDG |
E595103
|
entity |
| Predicate | missionAuthorization |
P79859
|
FINISHED |
| Object | national command authority |
—
|
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: national command authority | Statement: [NSWDG, missionAuthorization, national command authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionAuthorization Context triple: [NSWDG, missionAuthorization, national command authority]
-
A.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
B.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
C.
authorization
chosen
Indicates that one entity has granted another entity the right or permission to perform a specific action or access a particular resource.
-
D.
canAuthorize
Indicates that one entity has the power or permission to grant approval or official permission for another entity to perform an action or access a resource.
-
E.
accessMission
Indicates that an entity is permitted to enter, use, or interact with a specific mission or mission-related resources.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d7709e5881908f5d4c0dd9f818c9 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:55 p.m.