Triple
T4060948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murray family |
E86208
|
entity |
| Predicate | knownForPublishing |
P22589
|
FINISHED |
| Object | works of Lord Byron |
—
|
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: works of Lord Byron | Statement: [Murray family, knownForPublishing, works of Lord Byron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForPublishing Context triple: [Murray family, knownForPublishing, works of Lord Byron]
-
A.
notableAuthorPublished
Indicates that a work was published by an author who is recognized as notable or distinguished.
-
B.
publishesFor
chosen
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
C.
publishedAuthor
Indicates that a person is the author of one or more works that have been formally published.
-
D.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
E.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.