Triple
T33248941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream of the Red Chamber |
E851183
|
entity |
| Predicate | completionAttributedTo |
P17913
|
FINISHED |
| Object | Gao E |
—
|
NE NERFINISHED |
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: Gao E | Statement: [Dream of the Red Chamber, completionAttributedTo, Gao E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completionAttributedTo Context triple: [Dream of the Red Chamber, completionAttributedTo, Gao E]
-
A.
alsoCompletedBy
Indicates that the same task, activity, or item has been completed by an additional agent or entity besides the one already referenced.
-
B.
completionRelatedTo
Indicates that one entity’s completion, fulfillment, or finishing is connected to, dependent on, or relevant for another entity.
-
C.
creditedFor
chosen
Indicates that one entity is acknowledged as the source, contributor, or originator responsible for another entity (such as a work, achievement, or outcome).
-
D.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
E.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:31 a.m.