Triple
T356141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korea |
E7545
|
entity |
| Predicate | hasSpaceLaunchProgram |
P1426
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [North Korea, hasSpaceLaunchProgram, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpaceLaunchProgram Context triple: [North Korea, hasSpaceLaunchProgram, true]
-
A.
spaceProgram
chosen
Indicates that an entity is involved in, operates, or is associated with an organized program dedicated to space exploration, research, or related activities.
-
B.
spacecraftLaunchAssociatedWith
Indicates a relationship where a spacecraft launch is connected or linked to another event, object, or entity involved in or affected by that launch.
-
C.
successfulLaunches
Indicates that one entity has carried out one or more launches that achieved their intended objectives without failure.
-
D.
usedForSpaceLaunchScheduling
Indicates that something is utilized in planning, organizing, or timing activities related to launching spacecraft.
-
E.
spaceLaunchDestination
Indicates the target location or body in space toward which a space launch is directed.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebad8bf08190b4a38ffd9157d641 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e959ce948190a201c017eecb7c95 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.