Triple
T30890455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Six Swans |
E786882
|
entity |
| Predicate | relatedWorkByMotif |
P33019
|
FINISHED |
| Object | The Wild Swans |
E1328087
|
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: The Wild Swans | Statement: [The Six Swans, relatedWorkByMotif, The Wild Swans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkByMotif Context triple: [The Six Swans, relatedWorkByMotif, The Wild Swans]
-
A.
relatedWorkBySubject
Indicates a relationship where one work is connected to another through sharing the same subject or topic.
-
B.
relatedWorkByKey
Indicates a relationship where one work is linked or associated to another work identified by a specific key or identifier.
-
C.
relatedWorkByDedicatee
Indicates that a work is related to another work through the person to whom it is dedicated (the dedicatee).
-
D.
sharesMotifsWith
chosen
Indicates that two entities contain or employ similar recurring themes, patterns, or symbolic elements.
-
E.
relatedWorkByAttribution
Indicates that one work is connected to another through explicit attribution, such as citation, acknowledgment, or credit given by the creator or source.
- F. None of above.
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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28c7e78ebc819083fd321e93e5e6d8 |
completed | June 10, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:49 p.m.