Triple
T33607767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father of the Fatherland |
E860905
|
entity |
| Predicate | appliedHistoricallySinceCentury |
P262
|
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: [Father of the Fatherland, appliedHistoricallySinceCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedHistoricallySinceCentury Context triple: [Father of the Fatherland, appliedHistoricallySinceCentury, 16th century]
-
A.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
-
B.
observedSinceCentury
Indicates that one entity has been observed or documented as existing or occurring since a specified century.
-
C.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
D.
usedSinceCentury
chosen
Indicates that something has been in use starting from a specified century.
-
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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 1, 2026, 1:41 a.m.