Triple
T27155626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marchioness of Lorne |
E682510
|
entity |
| Predicate | historicalPeriodOfNotableUse |
P193108
|
FINISHED |
| Object | late 19th 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: late 19th century | Statement: [Marchioness of Lorne, historicalPeriodOfNotableUse, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfNotableUse Context triple: [Marchioness of Lorne, historicalPeriodOfNotableUse, late 19th century]
-
A.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
B.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
C.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
-
D.
historicalPeriodOfIndustrialUse
Indicates the historical time span during which an entity was used for industrial purposes.
-
E.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 27, 2026, 9:16 a.m.