Triple
T4383698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Rapporteur |
E99189
|
entity |
| Predicate | canCommunicateWith |
P43020
|
FINISHED |
| Object | governments |
—
|
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: governments | Statement: [Special Rapporteur, canCommunicateWith, governments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCommunicateWith Context triple: [Special Rapporteur, canCommunicateWith, governments]
-
A.
enablesCommunicationWith
Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
-
B.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
-
C.
communicationCapability
chosen
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
D.
enablesCommunicationBetween
Indicates that one entity provides the means or capability for communication to occur between two or more other entities.
-
E.
communicatesTo
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.