Triple
T1603213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 1373 |
E34440
|
entity |
| Predicate | enteredIntoEffect |
P448
|
FINISHED |
| Object | 2001-09-28 |
—
|
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: 2001-09-28 | Statement: [UN Security Council Resolution 1373, enteredIntoEffect, 2001-09-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredIntoEffect Context triple: [UN Security Council Resolution 1373, enteredIntoEffect, 2001-09-28]
-
A.
transitionedInto
Indicates that one entity changed state, form, role, or condition to become another specified state or entity.
-
B.
registrationEffect
Indicates the outcome or consequence that results from an entity being registered or from the act of registration taking place.
-
C.
sideEffectManagement
Indicates the relationship in which an action or intervention is used to monitor, reduce, or control the side effects caused by another action, treatment, or condition.
-
D.
enteredIntoForce
chosen
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
-
E.
enteredSpace
Indicates that an entity has moved into or crossed the boundary into a particular space or area.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.