Triple
T13890645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir William Bruce |
E333959
|
entity |
| Predicate | significantProjectStart |
P90421
|
FINISHED |
| Object | remodelling of Holyrood Palace in the 1670s |
—
|
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: remodelling of Holyrood Palace in the 1670s | Statement: [Sir William Bruce, significantProjectStart, remodelling of Holyrood Palace in the 1670s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantProjectStart Context triple: [Sir William Bruce, significantProjectStart, remodelling of Holyrood Palace in the 1670s]
-
A.
significantStartEvent
Indicates that an event marks an important or defining beginning point for a process, state, or relationship.
-
B.
majorProjectStartPeriod
chosen
Indicates the time period during which a major project is initiated or begins.
-
C.
significantPhaseStartEvent
Indicates the occurrence of an event that marks the beginning of an important or critical phase in a process or lifecycle.
-
D.
significantDevelopment
Indicates a development, change, or event that has substantial impact or importance within a given context or process.
-
E.
majorProject
Indicates that an entity is a primary, large-scale, or most significant project associated with another entity.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a3a24881908d81d634622fbbcc |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.