Triple
T36851403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest for Glory: So You Want to Be a Hero |
E910684
|
entity |
| Predicate | seriesFirstEntry |
P178303
|
FINISHED |
| Object | Quest for Glory |
—
|
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: Quest for Glory | Statement: [Quest for Glory: So You Want to Be a Hero, seriesFirstEntry, Quest for Glory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesFirstEntry Context triple: [Quest for Glory: So You Want to Be a Hero, seriesFirstEntry, Quest for Glory]
-
A.
seriesEntryOf
chosen
Indicates that one item functions as an individual entry, installment, or component within a larger series.
-
B.
seriesEntryType
Indicates the specific role or category that an item has within a series (e.g., main entry, supplemental entry, or related entry).
-
C.
firstSeries
Indicates that one entity is the initial or earliest series in an ordered sequence of related series.
-
D.
seriesDebutContext
Indicates the context or circumstances under which a series first debuted or was initially introduced.
-
E.
firstEpisode
Indicates that one entity is the initial or earliest episode in the series or sequence 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:13 p.m.