Triple
T20854396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frihetstiden |
E513441
|
entity |
| Predicate | timeInCentury |
P10925
|
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: [Frihetstiden, timeInCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInCentury Context triple: [Frihetstiden, timeInCentury, 18th century]
-
A.
completionCenturyGregorian
Indicates the century, in the Gregorian calendar system, during which the completion of something occurred.
-
B.
dateInCentury
Indicates that a specific date falls within the time span of a given century.
-
C.
testCenturies
Indicates that an entity has scored one or more centuries (100+ runs) in test cricket matches.
-
D.
convertedInCentury
Indicates that an entity underwent a conversion (e.g., religious, functional, or status change) during a specified century.
-
E.
timeLocatedInCentury
chosen
Indicates that an event or temporal entity occurs within, or is situated in, a specific 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a7113c819087994bcdfe643bc1 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.