Triple
T17032052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscountess Goschen |
E413222
|
entity |
| Predicate | statusDependsOn |
P125582
|
FINISHED |
| Object | marriage to the Viscount Goschen |
—
|
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: marriage to the Viscount Goschen | Statement: [Viscountess Goschen, statusDependsOn, marriage to the Viscount Goschen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDependsOn Context triple: [Viscountess Goschen, statusDependsOn, marriage to the Viscount Goschen]
-
A.
statusDetermines
Indicates that the status or condition of one entity determines or governs the state, outcome, or behavior of another entity.
-
B.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
statusDerivedFrom
Indicates that one entity’s status is obtained, inferred, or inherited from the status of another entity.
-
E.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d9e7d481909d3d5bd241bd68f1 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.