Triple
T23114974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acla |
E576723
|
entity |
| Predicate | approximateAbolitionCentury |
P14813
|
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: [Acla, approximateAbolitionCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateAbolitionCentury Context triple: [Acla, approximateAbolitionCentury, 16th century]
-
A.
approximateUseEndCentury
Indicates that something’s period of use ended around, but not necessarily exactly in, a specified century.
-
B.
declineBeganInCentury
Indicates that the period of decline for an entity started during a specified century.
-
C.
approximateCenturyBC
Indicates that something occurred or existed around a specified century before the start of the Common Era, with the time given as an approximate rather than exact century.
-
D.
adoptedInCentury
Indicates that something (such as a practice, idea, or object) was first adopted or came into use during a specified century.
-
E.
approximateStartCentury
chosen
Indicates the century in which something is estimated or roughly believed to have begun.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e11e9dc819093c569f388ffd46b |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.