Triple
T34513583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobbie |
E886087
|
entity |
| Predicate | setWithinTimePeriod |
P56370
|
FINISHED |
| Object | mid-20th century United States |
—
|
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 United States | Statement: [Bobbie, setWithinTimePeriod, mid-20th century United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWithinTimePeriod Context triple: [Bobbie, setWithinTimePeriod, mid-20th century United States]
-
A.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
B.
isSetInTimePeriod
chosen
Indicates that an event, story, or situation takes place within a specified time period.
-
C.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
D.
createsWithin
Indicates that one entity brings another entity into existence or produces it while operating inside the spatial, temporal, or contextual bounds of a specified containing entity.
-
E.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.