Triple
T4427372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roxburgh Castle |
E95240
|
entity |
| Predicate | changedHands |
P55934
|
FINISHED |
| Object | multiple times between Scotland and England |
—
|
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: multiple times between Scotland and England | Statement: [Roxburgh Castle, changedHands, multiple times between Scotland and England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedHands Context triple: [Roxburgh Castle, changedHands, multiple times between Scotland and England]
-
A.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
B.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
C.
handColor
Indicates that one entity has a specified color associated with its hand or hands.
-
D.
switchesPlacesWith
Indicates that two entities exchange their respective positions or roles with each other.
-
E.
reverseHandOffTo
Indicates transferring control, responsibility, or ownership of something back to the previous holder or source after it was handed off.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355674d5481908bf2dfd611f3520f |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.