Triple
T19748676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorare prayer |
E474317
|
entity |
| Predicate | centuryOfWidespreadUse |
P81534
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Memorare prayer, centuryOfWidespreadUse, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryOfWidespreadUse Context triple: [Memorare prayer, centuryOfWidespreadUse, 17th century]
-
A.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
B.
firstWidelyUsedDuring
chosen
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
-
C.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
-
D.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
E.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65296fa80819085aa4a18153531cf |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.