Triple
T12996806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Will Caster |
E322056
|
entity |
| Predicate | relationshipWithSpouse |
P33561
|
FINISHED |
| Object | research collaborator |
—
|
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: research collaborator | Statement: [Dr. Will Caster, relationshipWithSpouse, research collaborator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithSpouse Context triple: [Dr. Will Caster, relationshipWithSpouse, research collaborator]
-
A.
spouseRelationshipContext
Indicates a marital relationship context between two entities, specifying that they are spouses or partners in a recognized marriage-like union.
-
B.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
C.
spouseAssociatedWith
chosen
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
-
E.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
- F. None of above.
Provenance (3 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e7980288190a9fe629a8cc76a52 |
completed | April 10, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:45 p.m.