Triple
T22388446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/RES/662(1990) |
E553454
|
entity |
| Predicate | relatedToResolution |
P113405
|
FINISHED |
| Object | S/RES/660(1990) |
—
|
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: S/RES/660(1990) | Statement: [S/RES/662(1990), relatedToResolution, S/RES/660(1990)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToResolution Context triple: [S/RES/662(1990), relatedToResolution, S/RES/660(1990)]
-
A.
linkedToResolution
chosen
Indicates that something is associated with, or directly connected to, a specific resolution or decision outcome.
-
B.
followedByResolution
Indicates that one event, state, or action is directly succeeded by a resolving event, state, or action in a sequence.
-
C.
involvedResolution
Indicates that an entity participated in or contributed to the process of resolving a particular issue, conflict, or problem.
-
D.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
E.
relatedToClaimOf
Indicates a relationship where something is connected or pertinent to a specific claim or assertion.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15857fb588190b8180963aedd69c0 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.