Triple
T61917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter of the United Nations |
E1230
|
entity |
| Predicate | enteredIntoForceOn |
P448
|
FINISHED |
| Object | 1945-10-24 |
—
|
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: 1945-10-24 | Statement: [Charter of the United Nations, enteredIntoForceOn, 1945-10-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredIntoForceOn Context triple: [Charter of the United Nations, enteredIntoForceOn, 1945-10-24]
-
A.
enteredIntoForce
chosen
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
-
B.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
C.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
D.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
E.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251f74b0881909ad89127b8171277 |
completed | Feb. 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69a24ea242c8819086fe00bf01e6523e |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.