Triple
T6962643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Tait Black |
E161410
|
entity |
| Predicate | spouseFamilyBackground |
P5174
|
FINISHED |
| Object | Coats thread-manufacturing family |
—
|
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: Coats thread-manufacturing family | Statement: [James Tait Black, spouseFamilyBackground, Coats thread-manufacturing family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseFamilyBackground Context triple: [James Tait Black, spouseFamilyBackground, Coats thread-manufacturing family]
-
A.
spouseFamily
chosen
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
B.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spouseFrom
Indicates that one person is the spouse of another person originating from a specified place or source.
-
E.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daf197b0819085bd0433c8a7f716 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.