Triple
T26503568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Princess |
E669483
|
entity |
| Predicate | televisionSeriesRun |
P123538
|
FINISHED |
| Object | 1977–1986 |
—
|
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: 1977–1986 | Statement: [Pacific Princess, televisionSeriesRun, 1977–1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: televisionSeriesRun Context triple: [Pacific Princess, televisionSeriesRun, 1977–1986]
-
A.
notableSeriesRun
Indicates that an entity is recognized for having a significant or distinguished run within a particular series or sequence of events.
-
B.
networkSeriesRun
Indicates that a television series is broadcast or has its episodes aired on a particular network.
-
C.
televisionSeriesRuntimeCharacteristic
Indicates a relationship where a television series is associated with a specific runtime-related characteristic, such as typical episode length or overall duration pattern.
-
D.
timePeriodOfTelevisionSeries
chosen
Indicates the time span or era during which a television series is set or takes place.
-
E.
seriesRun
Indicates that one entity is a specific run, edition, or installment within an ongoing series associated with another 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6138baea48190b7c17200ea30aa7f |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:14 a.m.