Triple
T35338408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Pilgrim |
E1020527
|
entity |
| Predicate | settingPeriodContext |
P123135
|
FINISHED |
| Object | 19th century 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: 19th century England | Statement: [Mr. Pilgrim, settingPeriodContext, 19th century England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingPeriodContext Context triple: [Mr. Pilgrim, settingPeriodContext, 19th century England]
-
A.
settingPeriodDuration
Indicates the length of time for which a particular setting or configuration remains in effect.
-
B.
mainSettingPeriod
chosen
Indicates the historical or temporal period in which the primary setting of a work or event takes place.
-
C.
setsBaselinePeriod
Indicates that an entity establishes or defines a reference time span used as the baseline for comparison, measurement, or evaluation of subsequent periods.
-
D.
transitionPeriodContext
Indicates the contextual circumstances or conditions under which a transition period between states, phases, or regimes takes place.
-
E.
dstPeriod
Indicates the specific time period during which daylight saving time is in effect for a given entity or context.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:03 p.m.