Triple
T16581354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botolph |
E402837
|
entity |
| Predicate | notableBearerCentury |
P84738
|
FINISHED |
| Object | 7th 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: 7th century | Statement: [Botolph, notableBearerCentury, 7th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerCentury Context triple: [Botolph, notableBearerCentury, 7th century]
-
A.
hasNotableBearerCentury
chosen
Indicates that an entity has at least one notable bearer whose period of notability falls within the specified century.
-
B.
notableFromCentury
Indicates that an entity is notably associated with, or best known from, a particular century.
-
C.
associatedWithCenturyOfNameBearer
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
-
D.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
E.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35998371c8190936dcdaab5ca7e21 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.