Triple
T38429189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovat |
E903749
|
entity |
| Predicate | hasLaterHistoricalPeriod |
P3444
|
FINISHED |
| Object | early modern Scotland |
—
|
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 modern Scotland | Statement: [Lovat, hasLaterHistoricalPeriod, early modern Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterHistoricalPeriod Context triple: [Lovat, hasLaterHistoricalPeriod, early modern Scotland]
-
A.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
B.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
C.
hasHistoricalPrecursor
chosen
Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
-
D.
hasHistoricalSection
Indicates that something includes a dedicated part or segment that presents historical information or context.
-
E.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 3, 2026, 4:31 p.m.