Triple
T29711249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uganda State House |
E751787
|
entity |
| Predicate | hasProtocolFunction |
P105132
|
FINISHED |
| Object | hosting of visiting dignitaries |
—
|
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: hosting of visiting dignitaries | Statement: [Uganda State House, hasProtocolFunction, hosting of visiting dignitaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtocolFunction Context triple: [Uganda State House, hasProtocolFunction, hosting of visiting dignitaries]
-
A.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
B.
hasProtocolRole
Indicates that an entity participates in a protocol by fulfilling a specific role or function within that protocol.
-
C.
hasSubProtocol
Indicates that one protocol is a component, phase, or specialized part of another, more general protocol.
-
D.
hasServiceFunction
chosen
Indicates that an entity performs, provides, or is responsible for a particular service-related function or role.
-
E.
hasPublicFunction
Indicates that an entity possesses a function or method that is publicly accessible or callable from outside its defining scope.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: April 28, 2026, 7:30 p.m.