Triple
T336362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assembly of the League of Nations |
E6735
|
entity |
| Predicate | cannotMake |
P5771
|
FINISHED |
| Object | legally binding resolutions on member states |
—
|
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: legally binding resolutions on member states | Statement: [Assembly of the League of Nations, cannotMake, legally binding resolutions on member states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotMake Context triple: [Assembly of the League of Nations, cannotMake, legally binding resolutions on member states]
-
A.
canMake
chosen
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
B.
cannotReview
Indicates that an entity is not permitted or able to perform a review of another entity or item.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
canEnforce
Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon another entity.
-
E.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac950388190829875a07d821ddf |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94f049881908f10bb6548a8bb2e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.