Triple
T33989533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Searching |
E871504
|
entity |
| Predicate | sequelTypeOf |
P46331
|
FINISHED |
| Object | Missing is a spiritual sequel |
—
|
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: Missing is a spiritual sequel | Statement: [Searching, sequelTypeOf, Missing is a spiritual sequel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequelTypeOf Context triple: [Searching, sequelTypeOf, Missing is a spiritual sequel]
-
A.
hasSequelType
Indicates that one work has a sequel of a specified type or category in relation to another work.
-
B.
sequelGenreOfWork
Indicates that a work is a sequel belonging to the same or a specified genre as another work.
-
C.
sequelDirected
Indicates that one work is a sequel to another and was directed by the same director or a specific director associated with that sequel relationship.
-
D.
sequelWorkType
chosen
Indicates that the related work is a sequel and specifies the type or category of that sequel relationship between the works.
-
E.
sequelPlatform
Indicates that one platform is a follow-up or successor to another platform in a series or progression.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.