Triple
T32928802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bossiney |
E842342
|
entity |
| Predicate | firstRepresentationCentury |
P205202
|
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: [Bossiney, firstRepresentationCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRepresentationCentury Context triple: [Bossiney, firstRepresentationCentury, 16th century]
-
A.
firstReportedCentury
Indicates the century in which something was first reported or documented.
-
B.
firstPerformedCentury
Indicates the century in which an action, work, or performance was first carried out or presented.
-
C.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
firstClassCenturies
Indicates that the subject has scored one or more centuries (100 or more runs in a single innings) in first-class cricket matches.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:20 a.m.