Triple
T29921091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercy Croft |
E759938
|
entity |
| Predicate | relationshipToSisterGeorge |
P94755
|
FINISHED |
| Object | professional superior |
—
|
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: professional superior | Statement: [Mercy Croft, relationshipToSisterGeorge, professional superior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToSisterGeorge Context triple: [Mercy Croft, relationshipToSisterGeorge, professional superior]
-
A.
siblingOrRelative
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
B.
spouseOfSiblingOf
Indicates the person who is married to someone’s sibling.
-
C.
motherIsSisterOf
Indicates that the person who is the mother of one individual is also the sister of another individual.
-
D.
hasSisterRelationshipType
Indicates that there exists a sister-type familial relationship between the related entities.
-
E.
relationshipToRelative
chosen
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a01c51e2d088190b9dcce5b6de1cb9b |
completed | May 11, 2026, 12:01 p.m. |
| PD | Predicate disambiguation | batch_6a01c4c715a48190b7435de8a9d86fd4 |
completed | May 11, 2026, noon |
Created at: April 29, 2026, 6:14 p.m.