Triple
T16843179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kane and Abel |
E409463
|
entity |
| Predicate | hasWorkInSeriesOrder |
P88452
|
FINISHED |
| Object | first book in the Kane and Abel series |
—
|
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: first book in the Kane and Abel series | Statement: [Kane and Abel, hasWorkInSeriesOrder, first book in the Kane and Abel series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkInSeriesOrder Context triple: [Kane and Abel, hasWorkInSeriesOrder, first book in the Kane and Abel series]
-
A.
hasWorkInSeriesRole
Indicates that an entity holds a specific role or function within a particular work that is part of a series.
-
B.
hasWorkSeries
chosen
Indicates that one work belongs to, or is part of, a larger series of related works.
-
C.
hasPrecedingWork
Indicates that one work comes before another in a sequence, serving as its predecessor.
-
D.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
-
E.
hasWorkInSameSeries
Indicates that two works belong to and are part of the same 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b35284588190a1d6238438f3e70d |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.