Triple
T24920513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Belle Sauvage |
E624107
|
entity |
| Predicate | workInSeriesType |
P71621
|
FINISHED |
| Object | companion trilogy |
—
|
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: companion trilogy | Statement: [La Belle Sauvage, workInSeriesType, companion trilogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInSeriesType Context triple: [La Belle Sauvage, workInSeriesType, companion trilogy]
-
A.
worksInSeriesWith
Indicates that one entity collaborates or participates together with another entity within the same series or serialized work.
-
B.
workedOnSeries
Indicates that an entity contributed work to the creation or production of a particular series.
-
C.
hasWorkInSeriesRole
Indicates that an entity holds a specific role or function within a particular work that is part of a series.
-
D.
workSeriesConcept
chosen
Indicates that a work is part of, or related to, a broader series concept that groups multiple works together.
-
E.
sequelWorkType
Indicates that the related work is a sequel and specifies the type or category of that sequel relationship between the works.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:28 a.m.