Triple
T28975574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldritch Palmer |
E734401
|
entity |
| Predicate | relationshipWithTheMaster |
P146559
|
FINISHED |
| Object | servant |
—
|
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: servant | Statement: [Eldritch Palmer, relationshipWithTheMaster, servant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithTheMaster Context triple: [Eldritch Palmer, relationshipWithTheMaster, servant]
-
A.
relationshipToMaster
chosen
Indicates the type or nature of a subject’s connection, role, or association with a designated master entity.
-
B.
relationshipToMistressPage
Indicates a person’s specific relational role or connection to Mistress Page.
-
C.
wasDiscipleOf
Indicates that one entity served as a disciple, student, or follower under the guidance or teaching of another entity.
-
D.
masteredBy
Indicates that a subject (such as a skill, topic, or resource) has been fully learned, controlled, or become highly proficiently used by a particular agent or entity.
-
E.
isMasterOf
Indicates that one entity holds a position of control, authority, or ownership over another 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: April 28, 2026, 9:08 a.m.