Triple
T6533385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Wallace |
E152285
|
entity |
| Predicate | appointedGuardianOfScotland |
P71474
|
FINISHED |
| Object | 1297 |
—
|
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: 1297 | Statement: [William Wallace, appointedGuardianOfScotland, 1297]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedGuardianOfScotland Context triple: [William Wallace, appointedGuardianOfScotland, 1297]
-
A.
guardianDuringCommonwealth
Indicates that one entity served as the legal guardian of another during the period of the Commonwealth.
-
B.
lordChancellor
Indicates that one entity holds the position or role of Lord Chancellor in relation to another entity (such as a state, monarch, or government).
-
C.
appointedAs
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
-
D.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
-
E.
appointedBy
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbf3a748190b0fb52122faaf6d3 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:46 p.m.