Triple
T30461910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Charter Article 98 |
E775035
|
entity |
| Predicate | relatedToOrgan |
P151288
|
FINISHED |
| Object | United Nations Security Council |
E7539
|
NE 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: United Nations Security Council | Statement: [United Nations Charter Article 98, relatedToOrgan, United Nations Security Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToOrgan Context triple: [United Nations Charter Article 98, relatedToOrgan, United Nations Security Council]
-
A.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
C.
associatedOrgan
Indicates that one entity has a relevant connection or linkage to a particular organ, such as anatomical, functional, or pathological association.
-
D.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
E.
relationshipToOrganization
chosen
Indicates the nature or type of connection an entity has with a specific organization, such as affiliation, membership, or role.
- F. None of above.
Provenance (4 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a030c7d03308190a102689db1e8b657 |
completed | May 12, 2026, 11:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2798c765808190a0695d73586cf854 |
completed | June 9, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_6a030a57b16c81909191270f64a77fcf |
completed | May 12, 2026, 11:09 a.m. |
Created at: April 29, 2026, 8:10 p.m.