Triple
T9370897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hound of the Baskervilles |
E225526
|
entity |
| Predicate | firstSerialized |
P59503
|
FINISHED |
| Object | 1901 |
—
|
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: 1901 | Statement: [The Hound of the Baskervilles, firstSerialized, 1901]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSerialized Context triple: [The Hound of the Baskervilles, firstSerialized, 1901]
-
A.
firstSerialisedIn
Indicates the original publication or medium in which something (such as a work or story) was first released in serialized form.
-
B.
primarySerialization
Indicates that one representation or format of an entity is designated as its main or default form for storage, transmission, or processing.
-
C.
firstSeries
Indicates that one entity is the initial or earliest series in an ordered sequence of related series.
-
D.
firstSerializationYear
chosen
Indicates the year in which an entity (such as a work or series) was first serialized or began its initial serialized publication.
-
E.
originalSerialization
Indicates that one entity is the initial or source serialized form from which another serialized representation is derived.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5083cbb8819088e8cef26be1b380 |
completed | April 1, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.