Triple
T25886700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maw Maw |
E652206
|
entity |
| Predicate | relationshipToHopeChance |
P193986
|
FINISHED |
| Object | great-great-grandmother |
—
|
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: great-great-grandmother | Statement: [Maw Maw, relationshipToHopeChance, great-great-grandmother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHopeChance Context triple: [Maw Maw, relationshipToHopeChance, great-great-grandmother]
-
A.
relationshipToHeed
Indicates a relationship in which one entity is expected to pay attention to, respect, or follow the guidance, warnings, or wishes of another entity.
-
B.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
C.
relationshipImpact
Indicates how one entity’s relationship with another affects or changes those entities or their interaction.
-
D.
relationshipToBond
Indicates the specific type of personal, familial, or professional relationship an entity has to the person named Bond.
-
E.
relationshipPlannedWith
Indicates that a relationship between two entities has been intentionally arranged or scheduled to occur in the future.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: April 22, 2026, 8:18 a.m.