Triple
T24165687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Troy |
E598975
|
entity |
| Predicate | setInWorkPeriod |
P44456
|
FINISHED |
| Object | World War II era |
—
|
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: World War II era | Statement: [Virginia Troy, setInWorkPeriod, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInWorkPeriod Context triple: [Virginia Troy, setInWorkPeriod, World War II era]
-
A.
setInWorkBy
Indicates that something (such as a scene, event, or element) is situated or occurs within the context or setting of a particular work (such as a book, film, or other creative production).
-
B.
setWorkIn
Indicates that an entity assigns or places a work, task, or project into a particular context, location, or setting.
-
C.
hasWorkPeriodStart
Indicates the point in time when a specified work period begins.
-
D.
hasWorkPeriod
chosen
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
E.
workSettingPeriod
Indicates the time period during which a particular work setting or employment context is in effect.
- 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:32 p.m.