Triple
T23485961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 무궁화 |
E570532
|
entity |
| Predicate | canBePropagatedBy |
P11541
|
FINISHED |
| Object | 삽목 |
—
|
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: 삽목 | Statement: [무궁화, canBePropagatedBy, 삽목]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePropagatedBy Context triple: [무궁화, canBePropagatedBy, 삽목]
-
A.
canPropagate
Indicates that one entity is capable of transmitting, spreading, or extending another entity, state, or effect to additional targets or over a wider scope.
-
B.
cannotBePropagatedBy
Indicates that an effect, property, or condition associated with one entity cannot be transmitted, extended, or carried over to another entity.
-
C.
canBePassedTo
Indicates that one entity is capable of being transferred, handed over, or given to another entity.
-
D.
propagateAlong
Indicates that something (such as an effect, signal, or influence) spreads or is transmitted along a specified path, medium, or connection.
-
E.
propagationMethod
chosen
Indicates the means or mechanism by which something spreads, reproduces, or is transmitted from one entity or location to another.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7538a8c8190b7effcc39a3f9787 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.