Triple
T7463612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lismore Pace |
E176314
|
entity |
| Predicate | firstRunApprox |
P74271
|
FINISHED |
| Object | 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: 1970s | Statement: [Lismore Pace, firstRunApprox, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunApprox Context triple: [Lismore Pace, firstRunApprox, 1970s]
-
A.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
-
B.
firstRunTimePeriod
chosen
Indicates the initial time span or interval during which something first occurs, operates, or is in effect.
-
C.
firstRunProducer
Indicates that the producer is responsible for the initial or original run of a production, such as the first airing, release, or performance.
-
D.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
-
E.
firstRunViewership
Indicates the number of viewers who watched a program during its initial (first) broadcast or release.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d9d25c819087efc772b5b127fa |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.