Triple
T35854507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jimmy Barrett |
E1036458
|
entity |
| Predicate | spouseRelationshipDynamic |
P196518
|
FINISHED |
| Object | contentious marriage |
—
|
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: contentious marriage | Statement: [Jimmy Barrett, spouseRelationshipDynamic, contentious marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseRelationshipDynamic Context triple: [Jimmy Barrett, spouseRelationshipDynamic, contentious marriage]
-
A.
spouseRelationshipContext
Indicates a marital relationship context between two entities, specifying that they are spouses or partners in a recognized marriage-like union.
-
B.
spouseRelationshipType
chosen
Indicates the specific nature or category of a marital or spousal relationship between two individuals.
-
C.
relationshipToSpouse
Indicates the specific familial or social role one person holds in relation to their spouse (e.g., husband, wife, partner).
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.