Triple
T34867248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Best of Both Worlds (Star Trek: The Next Generation) |
E1005047
|
entity |
| Predicate | part2EpisodeNumberInSeason4 |
P142494
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [The Best of Both Worlds (Star Trek: The Next Generation), part2EpisodeNumberInSeason4, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: part2EpisodeNumberInSeason4 Context triple: [The Best of Both Worlds (Star Trek: The Next Generation), part2EpisodeNumberInSeason4, 1]
-
A.
partOfEP
chosen
Indicates that something is a component or segment of a larger episode or event process.
-
B.
episodeNumberInSeason
Indicates the specific sequential position an episode holds within a particular season of a series.
-
C.
partOfEpisodeCount
Indicates that one entity specifies the number of episodes contained within another entity (such as a season, series, or collection).
-
D.
episodeNumberInSeries
Indicates the specific sequential position an episode occupies within its overall series.
-
E.
episodeSeason
Indicates that an episode belongs to, or is part of, a specific season within a 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.