Triple
T1971530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orpington |
E42811
|
entity |
| Predicate | motheringAbility |
P33333
|
FINISHED |
| Object | good |
—
|
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: good | Statement: [Orpington, motheringAbility, good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motheringAbility Context triple: [Orpington, motheringAbility, good]
-
A.
possibleMother
Indicates that one entity could be the biological or adoptive mother of another, but this relationship is uncertain or not definitively established.
-
B.
maternalInfluence
Indicates the effect a mother or maternal figure has on shaping, guiding, or impacting another entity’s behavior, development, or state.
-
C.
possibleMotherOnly
Indicates that an entity is inferred or hypothesized to be the mother of another entity, but this relationship is not confirmed and remains only a possible maternal link.
-
D.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
-
E.
alternativeMother
Indicates that one entity serves as an alternative or substitute mother to another entity.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f275408190affa93f8cb6a8184 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb16a6db48190af04012e8ed2269f |
completed | March 7, 2026, 5:02 a.m. |
Created at: March 4, 2026, 7:36 p.m.