Triple
T21946013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H. W. Plainview |
E541934
|
entity |
| Predicate | settingTimePeriodOfWork |
P7950
|
FINISHED |
| Object | early 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: early 20th century | Statement: [H. W. Plainview, settingTimePeriodOfWork, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingTimePeriodOfWork Context triple: [H. W. Plainview, settingTimePeriodOfWork, early 20th century]
-
A.
workSettingPeriod
Indicates the time period during which a particular work setting or employment context is in effect.
-
B.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
-
C.
workPeriod
chosen
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
D.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
-
E.
workHoursLimit
Indicates a constraint on the maximum number of hours an entity is allowed or scheduled to work within a specified period.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12427c2b48190949c41bd3be2d9f3 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:57 p.m.