Triple
T28444605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The King’s Hospital |
E715804
|
entity |
| Predicate | movedToLocationInYear |
P113197
|
FINISHED |
| Object | Palmerstown, 1971 |
—
|
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: Palmerstown, 1971 | Statement: [The King’s Hospital, movedToLocationInYear, Palmerstown, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToLocationInYear Context triple: [The King’s Hospital, movedToLocationInYear, Palmerstown, 1971]
-
A.
movedToInYear
chosen
Indicates that an entity changed location or residence to a specified place in a particular year.
-
B.
movedAtAge
Indicates the age at which an entity changed residence or location.
-
C.
relocationYear
Indicates the year in which an entity was moved or transferred from one location to another.
-
D.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
E.
movedToCurrentLocationIn
Indicates that an entity changed its place or position and arrived at its current location during the specified time or event.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 1:48 a.m.