Triple
T27352790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Menteith |
E684406
|
entity |
| Predicate | titleInUseDuringCentury |
P141851
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Countess of Menteith, titleInUseDuringCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInUseDuringCentury Context triple: [Countess of Menteith, titleInUseDuringCentury, 13th century]
-
A.
titleInheritedInCentury
Indicates that a title was passed down or inherited during a specified century.
-
B.
titleHeldInCentury
chosen
Indicates that a particular title was held or in effect during a specified century.
-
C.
titleHolderStartCentury
Indicates the century in which an entity first began holding a particular title or position.
-
D.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
-
E.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 27, 2026, 11:49 a.m.