Triple
T30913689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Saudi Arabia |
E787522
|
entity |
| Predicate | associatedWithProtocol |
P64035
|
FINISHED |
| Object | royal protocol and etiquette |
—
|
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: royal protocol and etiquette | Statement: [Princess of Saudi Arabia, associatedWithProtocol, royal protocol and etiquette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithProtocol Context triple: [Princess of Saudi Arabia, associatedWithProtocol, royal protocol and etiquette]
-
A.
associatedProtocol
chosen
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
B.
associatedWithScheme
Indicates that one entity is linked or connected to a particular scheme, framework, or structured plan.
-
C.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
D.
relatedToProtocolVersion
Indicates a relationship where something is associated with, governed by, or dependent on a specific protocol version.
-
E.
associatedWithMode
Indicates a relationship in which something is linked or connected to a particular mode, method, or manner of operation or behavior.
- 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.