Triple
T32032196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishak |
E817995
|
entity |
| Predicate | servicePeriodContext |
P137524
|
FINISHED |
| Object | mid-1930s to early 1940s |
—
|
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-1930s to early 1940s | Statement: [Ishak, servicePeriodContext, mid-1930s to early 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servicePeriodContext Context triple: [Ishak, servicePeriodContext, mid-1930s to early 1940s]
-
A.
serviceEntryPeriod
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
B.
servedByTimePeriod
chosen
Indicates that a service, event, or activity occurs or is provided during a specified time period.
-
C.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
-
D.
sawServicePeriod
Indicates that one entity observed or was aware of the duration or specific period during which a service was provided or active.
-
E.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:18 a.m.