Triple
T5537388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Robin |
E145195
|
entity |
| Predicate | relationshipToMother |
P64797
|
FINISHED |
| Object | emotionally close and supportive |
—
|
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: emotionally close and supportive | Statement: [Jack Robin, relationshipToMother, emotionally close and supportive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMother Context triple: [Jack Robin, relationshipToMother, emotionally close and supportive]
-
A.
relationshipWithFather
Indicates a familial relationship that specifically connects an individual to their father.
-
B.
isMotherOf
Indicates that one entity is the female parent who has given birth to or legally/ socially parents the other entity.
-
C.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
D.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
E.
motherIs
Indicates that one entity is the mother (biological or adoptive) of 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fb19cb8819088b21e8ebef63d8b |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:34 p.m.