Triple
T28321558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldrick family |
E717290
|
entity |
| Predicate | settingAcrossGenerations |
P97897
|
FINISHED |
| Object | various historical periods |
—
|
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: various historical periods | Statement: [Baldrick family, settingAcrossGenerations, various historical periods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingAcrossGenerations Context triple: [Baldrick family, settingAcrossGenerations, various historical periods]
-
A.
settingOfLegacy
chosen
Indicates the context, environment, or circumstances in which a legacy is established, expressed, or carried forward.
-
B.
generationalControlOf
Indicates a relationship where one generation holds authority, influence, or decision-making power over another generation.
-
C.
settingAfter
Indicates that one setting or configuration occurs or is applied after another in a sequence or order.
-
D.
settingChange
Indicates a change made to a configuration, environment, or parameter value from one state to another.
-
E.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 12:24 a.m.