Triple
T12588264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Caversham |
E300525
|
entity |
| Predicate | historicalPeriodOfNotableHolder |
P65173
|
FINISHED |
| Object | early 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: early 18th century | Statement: [Viscount Caversham, historicalPeriodOfNotableHolder, early 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfNotableHolder Context triple: [Viscount Caversham, historicalPeriodOfNotableHolder, early 18th century]
-
A.
notableOfficePeriod
chosen
Indicates that an entity held a particular office or position during a specified time period.
-
B.
roleHistoricallyAssociatedWith
Indicates that one role, position, or function has been historically linked or commonly associated with another entity, role, or context over time.
-
C.
heldByDuringReignOf
Indicates that a position, title, or role was held by a person or entity specifically during the reign or rule of a particular sovereign or authority.
-
D.
notableFormerHolderRole
Indicates that an entity previously held a particular notable role or position.
-
E.
notableHistoricalEntity
Indicates that an entity holds recognized historical significance or prominence within a historical context.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:06 p.m.