Triple
T24186519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Basel |
E599570
|
entity |
| Predicate | residenceMovedTo |
P144745
|
FINISHED |
| Object | Porrentruy |
—
|
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: Porrentruy | Statement: [Prince-Bishop of Basel, residenceMovedTo, Porrentruy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceMovedTo Context triple: [Prince-Bishop of Basel, residenceMovedTo, Porrentruy]
-
A.
laterResidenceShiftOf
Indicates that one residence shift event occurs chronologically after another residence shift event for the same entity.
-
B.
movedPremises
Indicates that an entity has changed its location or base of operations from one set of premises to another.
-
C.
succeededByResidence
Indicates that one residence directly follows and replaces another as the primary place of dwelling for an entity.
-
D.
otherResidence
Indicates that an entity has an additional or alternative place of residence beyond its primary home.
-
E.
movedOn
chosen
Indicates that an entity changed its position or location from one place to another at some point in time.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.