Triple
T30913693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Saudi Arabia |
E787522
|
entity |
| Predicate | associatedWithSecurity |
P23332
|
FINISHED |
| Object | state-provided security |
—
|
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: state-provided security | Statement: [Princess of Saudi Arabia, associatedWithSecurity, state-provided security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSecurity Context triple: [Princess of Saudi Arabia, associatedWithSecurity, state-provided security]
-
A.
relatedSecurity
Indicates that one security has a defined relationship or association with another security, such as dependency, linkage, or relevance.
-
B.
alsoSecured
Indicates that an entity has obtained or provided additional security or collateral in connection with an existing secured obligation or arrangement.
-
C.
insecurityLinkedTo
Indicates a relationship where one entity’s insecurity is connected or attributed to another entity as a contributing factor or source.
-
D.
hasSecurityRelationship
chosen
Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of another entity.
-
E.
associatedWithUse
Indicates a relationship where one entity is connected to or involved in the use or utilization of 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:51 p.m.