Triple
T29895643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Adventures series |
E759269
|
entity |
| Predicate | firstTitle |
P84536
|
FINISHED |
| Object | Timewyrm: Genesys |
—
|
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: Timewyrm: Genesys | Statement: [New Adventures series, firstTitle, Timewyrm: Genesys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTitle Context triple: [New Adventures series, firstTitle, Timewyrm: Genesys]
-
A.
firstTitleFor
Indicates that one entity is the earliest or primary title assigned to another entity, typically among multiple possible titles.
-
B.
firstPartTitle
Indicates that one entity is the first part or initial segment of the title of another entity.
-
C.
firstSpecialTitle
Indicates that an entity holds or is assigned the earliest or primary special title in a sequence or set of titles.
-
D.
firstStoryTitle
chosen
Indicates that the associated value is the title of the first story in an ordered collection of stories.
-
E.
firstSeriesTitle
Indicates the title of the first series in which the subject (such as a work, character, or franchise) appears or to which it belongs.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a015ff02814819094806517fc4c69fa |
completed | May 11, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a0154ddd3c48190b85f9f48731cfd8f |
completed | May 11, 2026, 4:02 a.m. |
Created at: April 29, 2026, 6:04 p.m.