Triple
T14635459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Alexander |
E343592
|
entity |
| Predicate | appearsInSettingPeriod |
P97182
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [David Alexander, appearsInSettingPeriod, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInSettingPeriod Context triple: [David Alexander, appearsInSettingPeriod, mid-20th century]
-
A.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
-
B.
appearedThroughPeriod
Indicates that an entity was present or manifested continuously or recurrently throughout a specified time period.
-
C.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
D.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
E.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ab9578819085b4cf7244d30d87 |
completed | April 14, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.