Triple
T30598207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Roarke |
E778840
|
entity |
| Predicate | primaryTimePeriodOfSeries |
P138941
|
FINISHED |
| Object | late 1970s |
—
|
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: late 1970s | Statement: [Mr. Roarke, primaryTimePeriodOfSeries, late 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTimePeriodOfSeries Context triple: [Mr. Roarke, primaryTimePeriodOfSeries, late 1970s]
-
A.
timePeriodInSeries
chosen
Indicates the specific time span or interval during which an installment, episode, or part occurs within a larger series or sequence.
-
B.
primaryServicePeriod
Indicates the main or most significant span of time during which a service, duty, or activity is performed or in effect.
-
C.
representedPeriodStart
Indicates the starting point in time of the period that the subject is intended to represent.
-
D.
primaryCollectionPeriod
Indicates the main time span during which data, items, or observations are initially collected or gathered.
-
E.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0309a4e4d481908a6070b40d507aae |
completed | May 12, 2026, 11:06 a.m. |
| PD | Predicate disambiguation | batch_6a03091ac1008190bf50357364d4e9e4 |
completed | May 12, 2026, 11:03 a.m. |
Created at: April 29, 2026, 8:24 p.m.