Triple
T3249745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At the ’Cadian Ball |
E68146
|
entity |
| Predicate | relatedWorkRelation |
P922
|
FINISHED |
| Object | prequel to The Storm |
—
|
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: prequel to The Storm | Statement: [At the ’Cadian Ball, relatedWorkRelation, prequel to The Storm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkRelation Context triple: [At the ’Cadian Ball, relatedWorkRelation, prequel to The Storm]
-
A.
associatedWork
chosen
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
B.
relatedWorkCreator
Indicates that the creator of one work is related (e.g., by authorship, contribution, or collaboration) to the creation of another work.
-
C.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of another entity.
-
D.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
E.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf3fc3c8819080ac95974581ca0e |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.