Triple
T27155611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marchioness of Lorne |
E682510
|
entity |
| Predicate | startTimeOfNotableHolding |
P34618
|
FINISHED |
| Object | 1871 |
—
|
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: 1871 | Statement: [Marchioness of Lorne, startTimeOfNotableHolding, 1871]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfNotableHolding Context triple: [Marchioness of Lorne, startTimeOfNotableHolding, 1871]
-
A.
startTimeOfNotableRole
chosen
Indicates the point in time when an entity began a notable role, position, or function.
-
B.
firstHeldAt
Indicates the initial time or event at which an entity was first held, possessed, or hosted.
-
C.
notableManagerTenureStart
Indicates the date or point in time when a manager’s particularly significant or distinguished period of managing an entity began.
-
D.
firstHeldFor
Indicates the initial time period or event during which an entity was first held, possessed, or hosted by another entity.
-
E.
firstHeldAfter
Indicates that one entity’s first instance of holding or possessing something occurred later in time than another entity’s first such instance.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 9:16 a.m.