Triple
T24771591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Lavery |
E619738
|
entity |
| Predicate | introducedOnSeries |
P8259
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Duke Lavery, introducedOnSeries, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedOnSeries Context triple: [Duke Lavery, introducedOnSeries, 1980s]
-
A.
introducedForSeries
Indicates that an entity was first created or brought into existence specifically for inclusion in a particular series.
-
B.
introducedOnTV
Indicates that an entity was first presented, revealed, or made known to the public through a television broadcast.
-
C.
introducedOnNetwork
Indicates that an entity was first presented, debuted, or made available on a particular network.
-
D.
introducedToSeries
Indicates that one entity caused or enabled another entity to first encounter, become aware of, or start engaging with a particular series.
-
E.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:31 a.m.