Triple
T16620144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josh Mostel |
E403801
|
entity |
| Predicate | hasWorkPeriodStart |
P123585
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Josh Mostel, hasWorkPeriodStart, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkPeriodStart Context triple: [Josh Mostel, hasWorkPeriodStart, 1960s]
-
A.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
B.
containsWorkFromPeriod
Indicates that something includes or features work that originates from a specified historical or temporal period.
-
C.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
D.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
E.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
- F. None of above. chosen
Provenance (4 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754c934c8190a0a8ddd747681aa7 |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.