Triple
T7246107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scots Wha Hae |
E156473
|
entity |
| Predicate | periodWrittenIn |
P75539
|
FINISHED |
| Object | 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: 18th century | Statement: [Scots Wha Hae, periodWrittenIn, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodWrittenIn Context triple: [Scots Wha Hae, periodWrittenIn, 18th century]
-
A.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
B.
laterWrittenIn
Indicates that one text or version was written at a later time than another, establishing a chronological order between the writings.
-
C.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
-
D.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
E.
writtenInCountry
Indicates that a written work was created, authored, or composed within the geographical boundaries of a specific country.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea5a8bbc8190bf16747dbdd65ce8 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:56 p.m.