Triple
T24844157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron of Branksome |
E621696
|
entity |
| Predicate | firstPublicationOfWorkFeaturingSubject |
P126289
|
FINISHED |
| Object | 1805 |
—
|
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: 1805 | Statement: [Baron of Branksome, firstPublicationOfWorkFeaturingSubject, 1805]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicationOfWorkFeaturingSubject Context triple: [Baron of Branksome, firstPublicationOfWorkFeaturingSubject, 1805]
-
A.
firstPublishedWork
Indicates that one work is the earliest piece created or released by a particular creator or entity.
-
B.
firstPublicationUnderName
Indicates that an entity’s first publication occurred using a specified name (e.g., pseudonym, pen name, or new legal name).
-
C.
workFirstPublicationApproximate
Indicates that the date of a work’s first publication is not exact but an approximate or estimated value.
-
D.
firstPublicationIn
Indicates the initial venue, medium, or context in which a work was first published.
-
E.
firstPublicationOfContainingWork
chosen
Indicates that the related entity is the earliest published work in which the referenced work or content first appeared.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 5:19 a.m.