Triple
T18144434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gresham family |
E434346
|
entity |
| Predicate | recursAcrossSeries |
P121478
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Gresham family, recursAcrossSeries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recursAcrossSeries Context triple: [The Gresham family, recursAcrossSeries, true]
-
A.
recursAs
Indicates that an event, pattern, or condition appears again over time in the same or a similar form.
-
B.
recurringSeries
chosen
Indicates that an event, action, or pattern occurs repeatedly over time as part of an ongoing series rather than as a one-time instance.
-
C.
recursIn
Indicates that an event, pattern, or entity appears repeatedly or returns multiple times within a given context, sequence, or timeframe.
-
D.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
E.
seriesWith
Indicates that one entity is part of, or grouped together in, the same series or sequence as 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de32d3f88190bd9f406729716407 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.