Triple
T33474371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ava in Nashville |
E857278
|
entity |
| Predicate | previousNetworkOfSeries |
P112340
|
FINISHED |
| Object | ABC |
—
|
NE NERFINISHED |
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: ABC | Statement: [Ava in Nashville, previousNetworkOfSeries, ABC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNetworkOfSeries Context triple: [Ava in Nashville, previousNetworkOfSeries, ABC]
-
A.
originalNetworkOfRelatedSeries
Indicates that a series served as the original network broadcaster for another, related series.
-
B.
networkOfSeries
Indicates a relationship where multiple series are interconnected or grouped together as part of the same network or collection.
-
C.
networkOfParentSeries
Indicates that one series is part of, or derived from, a broader parent series within a networked or hierarchical series structure.
-
D.
originalNetworkForSeries
Indicates the television network on which a series was first originally broadcast or premiered.
-
E.
precededByNetworkForSeries
chosen
Indicates that one network chronologically aired or was associated with a series before another network for that same series.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 1, 2026, 1:37 a.m.