Triple
T58427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. President |
E1156
|
entity |
| Predicate | usedInProtocol |
P3331
|
FINISHED |
| Object | diplomatic protocol |
—
|
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: diplomatic protocol | Statement: [Mr. President, usedInProtocol, diplomatic protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInProtocol Context triple: [Mr. President, usedInProtocol, diplomatic protocol]
-
A.
usesProtocolSuite
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
B.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
C.
usedInDomain
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24c9057348190aa6692eeeae19569 |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac7547c81909bb68f327cdb9158 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c8fa20c8190aacc38e53d1f654c |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.