Triple
T25628958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casket Letters |
E642520
|
entity |
| Predicate | custodyHistory |
P22003
|
FINISHED |
| Object | later transferred to 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: later transferred to England | Statement: [Casket Letters, custodyHistory, later transferred to England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: custodyHistory Context triple: [Casket Letters, custodyHistory, later transferred to England]
-
A.
custody
Indicates having legal responsibility and authority over the care and control of another entity, typically a child or dependent.
-
B.
ownershipHistory
chosen
Indicates the sequence of past and present owners associated with an entity over time.
-
C.
historicalFamilyPlacement
Indicates the recorded arrangement or position of an individual within a family structure at some point in the past.
-
D.
tenantHistory
Indicates a record of past and/or current tenancy relationships associated with an entity, such as previous tenants, lease periods, and related rental details.
-
E.
subsequentHistory
Indicates that one event, state, or record occurs or is recorded after another in time, reflecting its later historical development or outcome.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa260734819080d7d32c6912d267 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 5:16 p.m.