Triple
T23494405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolesław I the Tall |
E571662
|
entity |
| Predicate | returnedToRule |
P116962
|
FINISHED |
| Object | Silesia in 1163 |
—
|
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: Silesia in 1163 | Statement: [Bolesław I the Tall, returnedToRule, Silesia in 1163]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToRule Context triple: [Bolesław I the Tall, returnedToRule, Silesia in 1163]
-
A.
returnedToRole
chosen
Indicates that an entity resumed or went back to a role or position it previously held.
-
B.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
C.
returnedToUse
Indicates that something previously inactive, unavailable, or discontinued has been put back into active use or operation.
-
D.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
E.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7def8ac8190ade511299078d55b |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.