Triple
T23762649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mermaid Chair |
E587292
|
entity |
| Predicate | exploresMotherDaughterRelationship |
P153868
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Mermaid Chair, exploresMotherDaughterRelationship, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresMotherDaughterRelationship Context triple: [The Mermaid Chair, exploresMotherDaughterRelationship, true]
-
A.
relationshipToMother
Indicates the specific familial or social connection an entity has to its mother.
-
B.
interpretationOfMother
Indicates a relationship where something is understood, portrayed, or taken as a representation or role of a mother.
-
C.
motherRole
Indicates that one entity holds the role or function of a mother in relation to another entity.
-
D.
maternalConnectionTo
Indicates a relationship in which one entity is the mother of, or has a motherly bond or role toward, another entity.
-
E.
motherMentionedIn
Indicates that an entity’s mother is referenced or mentioned within another entity (such as a text, record, or communication).
- F. None of above. chosen
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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb34d5c81909087385066a52e61 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:14 p.m.