Triple
T7296293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Ambassador to the Holy See |
E164528
|
entity |
| Predicate | usesProtocolTitle |
P10405
|
FINISHED |
| Object | His Excellency |
—
|
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: His Excellency | Statement: [Austrian Ambassador to the Holy See, usesProtocolTitle, His Excellency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProtocolTitle Context triple: [Austrian Ambassador to the Holy See, usesProtocolTitle, His Excellency]
-
A.
usesTitle
chosen
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
B.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
-
C.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
D.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
E.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8d0c6c8190b32cd08b9a5d96cc |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.