Triple
T6936132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bannatyne Manuscript |
E160557
|
entity |
| Predicate | compiledDuring |
P9915
|
FINISHED |
| Object | plague of 1568 in Edinburgh |
—
|
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: plague of 1568 in Edinburgh | Statement: [The Bannatyne Manuscript, compiledDuring, plague of 1568 in Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compiledDuring Context triple: [The Bannatyne Manuscript, compiledDuring, plague of 1568 in Edinburgh]
-
A.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
B.
constructedDuring
chosen
Indicates that one entity was built or created within the time period defined by another entity or event.
-
C.
compiledUnder
Indicates that something (typically code or a program) was built or translated into executable form using a specific compiler, configuration, or compilation environment.
-
D.
compiledAt
Indicates that one entity was built or transformed into an executable or final form at a specific time or location represented by the other entity.
-
E.
compiledInPeriod
Indicates that the creation or compilation of something occurred within a specified time period.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:27 p.m.