Triple
T3811368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald III of Scotland |
E93141
|
entity |
| Predicate | coRuleStart |
P51984
|
FINISHED |
| Object | 1094 |
—
|
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: 1094 | Statement: [Donald III of Scotland, coRuleStart, 1094]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRuleStart Context triple: [Donald III of Scotland, coRuleStart, 1094]
-
A.
startRule
Indicates that a particular rule is the initial or entry rule from which a process, system, or evaluation begins.
-
B.
startOfRule
Indicates that one element marks the beginning boundary or initial segment of a specified rule.
-
C.
deFactoRuleStart
Indicates the point in time or condition at which a rule begins to apply in practice, regardless of its formal or official start.
-
D.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
E.
startRuleRegion
Indicates the point or condition at which a defined rule’s area of applicability or operational scope begins.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:16 p.m.