Triple
T3811369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald III of Scotland |
E93141
|
entity |
| Predicate | coRuleEnd |
P14957
|
FINISHED |
| Object | 1097 |
—
|
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: 1097 | Statement: [Donald III of Scotland, coRuleEnd, 1097]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRuleEnd Context triple: [Donald III of Scotland, coRuleEnd, 1097]
-
A.
endRule
chosen
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
B.
typicalEndRule
Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
-
C.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
D.
cutRule
Indicates that one entity applies or enforces a rule that removes, prunes, or eliminates certain elements or possibilities from consideration.
-
E.
endRuleRegion
Indicates the point at which a previously defined rule’s applicable region or scope terminates.
- 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_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. |
Created at: March 9, 2026, 3:16 p.m.