Triple
T31778432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 26 of the United Nations Charter |
E811126
|
entity |
| Predicate | mentionsOrgan |
P36517
|
FINISHED |
| Object | Military Staff Committee |
—
|
NE NERFINISHED |
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: Military Staff Committee | Statement: [Article 26 of the United Nations Charter, mentionsOrgan, Military Staff Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsOrgan Context triple: [Article 26 of the United Nations Charter, mentionsOrgan, Military Staff Committee]
-
A.
mentionsOrganization
chosen
Indicates that one entity refers to, cites, or otherwise brings up an organization in its content or communication.
-
B.
mentions
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
C.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
D.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
E.
mentionsSee
Indicates that one entity explicitly refers to or cites another entity within its content.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:35 p.m.