Triple
T31179276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. James Mortimer |
E794842
|
entity |
| Predicate | bringsDocument |
P171352
|
FINISHED |
| Object | manuscript about the Baskerville curse |
—
|
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: manuscript about the Baskerville curse | Statement: [Dr. James Mortimer, bringsDocument, manuscript about the Baskerville curse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bringsDocument Context triple: [Dr. James Mortimer, bringsDocument, manuscript about the Baskerville curse]
-
A.
discussedDocument
Indicates that an entity has engaged in a discussion about a particular document.
-
B.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
-
C.
linkedDocument
Indicates that one document is associated with or references another document in a meaningful way.
-
D.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
E.
documentAtIssue
Indicates that a particular document is the specific item under consideration or dispute in a given context or proceeding.
- F. None of above. chosen
Provenance (4 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:08 p.m.