Triple
T14756791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of Fiji |
E346749
|
entity |
| Predicate | formalCommunicationChannel |
P19806
|
FINISHED |
| Object | address to Parliament |
—
|
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: address to Parliament | Statement: [President of Fiji, formalCommunicationChannel, address to Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalCommunicationChannel Context triple: [President of Fiji, formalCommunicationChannel, address to Parliament]
-
A.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
B.
formalFunction
Indicates that an entity serves an official or designated role or purpose within a formal structure, system, or context.
-
C.
formalContent
chosen
Indicates that the content is expressed in a formal, structured, or official manner, as opposed to casual or informal expression.
-
D.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
E.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7ef0fd48190bd4a8af128ef274c |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.