Triple
T37799952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufus |
E942343
|
entity |
| Predicate | hasMotherDescribedAs |
P200934
|
FINISHED |
| Object | a mother to Paul |
—
|
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: a mother to Paul | Statement: [Rufus, hasMotherDescribedAs, a mother to Paul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotherDescribedAs Context triple: [Rufus, hasMotherDescribedAs, a mother to Paul]
-
A.
motherWas
Indicates that one entity was the mother (biological or adoptive) of another entity at some time in the past.
-
B.
motherIs
Indicates that one entity is the mother (biological or adoptive) of another entity.
-
C.
isMotherOf
Indicates that one entity is the female parent who has given birth to or legally/ socially parents the other entity.
-
D.
hasMotherOrigin
Indicates that an entity’s origin, source, or lineage is derived from or attributed to a mother 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69ffb97ae1508190bf3addd6e2aac281 |
completed | May 9, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:19 p.m.