Triple
T13508608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monarchy (TV series) |
E321077
|
entity |
| Predicate | hasEpisodeCountPerSeries |
P110039
|
FINISHED |
| Object | varies by series |
—
|
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: varies by series | Statement: [Monarchy (TV series), hasEpisodeCountPerSeries, varies by series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpisodeCountPerSeries Context triple: [Monarchy (TV series), hasEpisodeCountPerSeries, varies by series]
-
A.
hasEpisodeCountInFirstSeries
Indicates that an entity has a specific number of episodes in its first series or season.
-
B.
numberOfSeriesPerSeason
Indicates the total count of series (or episodes/instalments) that occur within a single season of something.
-
C.
numberOfEpisodes
Indicates the total count of episodes associated with a given entity, such as a series or season.
-
D.
hasEpisodeStructure
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
E.
hasEpisode
Indicates that something, typically a series or program, includes a specific episode as one of its constituent parts.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf85a74081909eb08751fc55ce8f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaee128d88190b097be17fdd2f92b |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.