Triple
T33061546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederica |
E845985
|
entity |
| Predicate | hasPeakUsageCentury |
P86226
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Frederica, hasPeakUsageCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakUsageCentury Context triple: [Frederica, hasPeakUsageCentury, 18th century]
-
A.
reachedPeakInCentury
chosen
Indicates that something attained its highest level, influence, or development during a specified century.
-
B.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
-
C.
observedSinceCentury
Indicates that one entity has been observed or documented as existing or occurring since a specified century.
-
D.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
E.
hasHistoricHundred
Indicates that an entity has achieved a notable score of 100 (a "hundred") in a historic or particularly significant context.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:25 a.m.