Triple
T16127188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miraculous Medal |
E391300
|
entity |
| Predicate | spreadRapidlyIn |
P9468
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Miraculous Medal, spreadRapidlyIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spreadRapidlyIn Context triple: [Miraculous Medal, spreadRapidlyIn, 19th century]
-
A.
spreadingStatus
Indicates the current state or progression of how something is spreading or being disseminated (e.g., whether and how it is expanding, stable, or declining).
-
B.
spreadTo
chosen
Indicates that something extends, propagates, or is transmitted from one entity, location, or context to another.
-
C.
spreadBy
Indicates that something is transmitted, dispersed, or propagated through the agency or action of a specified entity or medium.
-
D.
expandedRapidly
Indicates that an entity’s size, scope, or intensity increased significantly within a short period of time.
-
E.
epidemicSpreadFrom
Indicates that an epidemic originates in one location or population and then spreads to another location or population.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20205bed48190a6930439738da191 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.