Triple
T18512152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paston |
E452366
|
entity |
| Predicate | sourceTypeForHistory |
P38247
|
FINISHED |
| Object | family correspondence |
—
|
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: family correspondence | Statement: [Paston, sourceTypeForHistory, family correspondence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceTypeForHistory Context triple: [Paston, sourceTypeForHistory, family correspondence]
-
A.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
B.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
C.
usesSourceType
chosen
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
D.
mainSourceType
Indicates the primary category or kind of source from which something originates or is derived.
-
E.
hasTypeOfSource
Indicates that one entity is classified as a particular kind or category of source in relation to another entity.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53346f9488190bc2e4570564bede0 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.