Triple
T6041757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Consort of the United Kingdom |
E134561
|
entity |
| Predicate | notAutomaticallyGranted |
P68336
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Prince Consort of the United Kingdom, notAutomaticallyGranted, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAutomaticallyGranted Context triple: [Prince Consort of the United Kingdom, notAutomaticallyGranted, true]
-
A.
cannotGrant
Indicates that an entity lacks the authority, permission, or ability to confer a requested right, access, or resource to another entity.
-
B.
notAuthorizedFor
Indicates that an entity lacks the required permission or authority to perform a specific action or access a particular resource.
-
C.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
D.
notRestrictedBy
Indicates that something is free from limitations, constraints, or prohibitions imposed by another entity or condition.
-
E.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056d11370819096ac35349bd91f4e |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:08 p.m.