Triple
T875447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNAIDS |
E18907
|
entity |
| Predicate | isCosponsoredBy |
P3260
|
FINISHED |
| Object | 11 UN system organizations |
—
|
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: 11 UN system organizations | Statement: [UNAIDS, isCosponsoredBy, 11 UN system organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCosponsoredBy Context triple: [UNAIDS, isCosponsoredBy, 11 UN system organizations]
-
A.
coSponsor
chosen
Indicates that an entity jointly supports, endorses, or backs an initiative, proposal, or activity together with one or more others.
-
B.
sponsoredInSenateBy
Indicates that a legislative measure or proposal was formally introduced or championed in the Senate by a specific senator.
-
C.
isBipartisan
Indicates that an action, decision, or stance is supported or undertaken by members of two (or more) opposing political parties.
-
D.
coSignedWith
Indicates that an entity has jointly signed a document, agreement, or obligation together with another entity.
-
E.
isBicameralPartnerOf
Indicates that one legislative body or chamber forms one of the two cooperating parts of a bicameral partnership with another.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acae12948190923d31966c26a130 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.