Triple
T29741678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles III of Scotland |
E752624
|
entity |
| Predicate | claimedDuringConflict |
P151459
|
FINISHED |
| Object | Jacobite rising of 1745 |
—
|
NE NERFINISHED |
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: Jacobite rising of 1745 | Statement: [Charles III of Scotland, claimedDuringConflict, Jacobite rising of 1745]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedDuringConflict Context triple: [Charles III of Scotland, claimedDuringConflict, Jacobite rising of 1745]
-
A.
claimedDuring
chosen
Indicates that an assertion or claim was made within a specific time period or event interval.
-
B.
heldDuringConflict
Indicates that an entity maintained control, possession, or occupation of something for some duration while an identified conflict was ongoing.
-
C.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
D.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
E.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 7:48 p.m.