Triple
T4841436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hail Mary |
E108188
|
entity |
| Predicate | fullyStandardizedByCentury |
P4436
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Hail Mary, fullyStandardizedByCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullyStandardizedByCentury Context triple: [Hail Mary, fullyStandardizedByCentury, 16th century]
-
A.
standardizedInCentury
chosen
Indicates that something was standardized or formally established according to a common norm during a specified century.
-
B.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
C.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
D.
laterStandardization
Indicates that one entity becomes standardized or formally established at a later time than another entity.
-
E.
attestedFromCentury
Indicates the century from which there is evidence or documentation that something is known to exist or be in use.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.