Triple
T33661017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Golden Treasury |
E862350
|
entity |
| Predicate | notableEditorCollaboration |
P206623
|
FINISHED |
| Object | Alfred Tennyson |
E58639
|
NE 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: Alfred Tennyson | Statement: [The Golden Treasury, notableEditorCollaboration, Alfred Tennyson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEditorCollaboration Context triple: [The Golden Treasury, notableEditorCollaboration, Alfred Tennyson]
-
A.
notableEditor
Indicates that an entity has served as a significant or distinguished editor of another entity, such as a publication or work.
-
B.
notableCollaboration
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
-
C.
bearerNotableCollaboration
Indicates that the bearer is significantly associated with a noteworthy collaboration or joint work involving another entity.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
commonlyEditedWith
Indicates that two entities are frequently modified or edited together within the same context or workflow.
- F. None of above. chosen
Provenance (5 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a362727f5348190a022bc72b82c87f2 |
completed | June 20, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.