Triple
T27818093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maple LaMarsh |
E702735
|
entity |
| Predicate | timeSettingOfWork |
P32393
|
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: [Maple LaMarsh, timeSettingOfWork, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSettingOfWork Context triple: [Maple LaMarsh, timeSettingOfWork, World War II era]
-
A.
workSettingPeriod
chosen
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.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
-
D.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6386cb0a08190aa7300c319d83884 |
completed | May 2, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:46 p.m.