Triple
T38274955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Henderson |
E1021920
|
entity |
| Predicate | relationshipToBea |
P204574
|
FINISHED |
| Object | son |
—
|
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: son | Statement: [Jeff Henderson, relationshipToBea, son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToBea Context triple: [Jeff Henderson, relationshipToBea, son]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
relationshipToBond
Indicates the specific type of personal, familial, or professional relationship an entity has to the person named Bond.
-
C.
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.
-
D.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.