Triple
T2134191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narragansett language |
E46611
|
entity |
| Predicate | documentationCentury |
P35019
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Narragansett language, documentationCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationCentury Context triple: [Narragansett language, documentationCentury, 17th century]
-
A.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
B.
publicationCentury
Indicates the century during which a work was published.
-
C.
testCenturies
Indicates that an entity has scored one or more centuries (100+ runs) in test cricket matches.
-
D.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
E.
historicalFormulationCentury
Indicates the century during which something was originally formulated or first established.
- F. None of above. chosen
Provenance (4 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba24004819091ffb9440e8615fa |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb860a51c8190b4ae3bb1cedc0fa0 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:44 p.m.